Managing Storage Adapters

Self Encrypting Drives (Full Disk Encryption)

Cisco IMC supports self encrypting drives (SED). A special hardware in the drives encrypts incoming data and decrypts outgoing data in real-time. This feature is also called Full Disk Encryption (FDE).

The data on the drive is encrypted on its way into the drive and decrypted on its way out. However, if you lock the drive, no security key is required to retrieve the data.

When a drive is locked, an encryption key is created and stored internally. All data stored on this drive is encrypted using that key, and stored in encrypted form. Once you store the data in this manner, a security key is required in order to un-encrypt and fetch the data from the drive. Unlocking a drive deletes that encryption key and renders the stored data unusable. This is called a Secure Erase. The FDE comprises a key ID and a security key.

The FDE feature supports the following operations:

  • Enable and disable security on a controller

  • Create a secure virtual drive

  • Secure a non-secure drive group

  • Unlock foreign configuration drives

  • Enable security on a physical drive (JBOD)

  • Clear secure SED drives

  • Clear secure foreign configuration

Scenarios to consider While Configuring Controller Security in a Dual or Multiple Controllers Environment


Note

Dual or Multiple controllers connectivity is available only on some servers.

Controller security can be enabled, disabled, or modified independently. However, local and remote key management applies to all the controllers on the server. Therefore security action involving switching the key management modes must be performed with caution. In a scenario where both controllers are secure, and you decide to move one of the controllers to a different mode, you need to perform the same operation on the other controller as well.

Consider the following two scenarios:

  • Scenario 1—Key management is set to remote; both controllers are secure and use remote key management. If you now wish to switch to local key management, switch the key management for each controller and disable remote key management.

  • Scenario 2—Key management is set to local; both controllers are secure and use local key management. If you now wish to switch to remote key management, enable remote key management and switch the key management for each controller.

If you do not modify the controller security method on any one of the controllers, it renders the secure key management in an unsupported configuration state.

Enabling Controller Security

Before you begin

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

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

In the Actions drop-down list on the right pane, click Storage > Enable Drive Security.

The Enable Drive Security dialog box appears.

Step 4

In the Enable Drive Security dialog box, review the following information:

Name Description

Controller Security field

Indicates whether or not controller security is enabled. This can be one of the following:

  • True— Controller security is enabled.

  • False— Controller security is disabled.

Security Key Identifier field

The current key ID.

Security Key field

Security key used to enable controller security. If you wish to change the current security key, enter the new key here.

Note

 

Once you change the security key, a Secure Key Verification pop-up window appears where you need to enter the current security key to verify it.

Confirm Security Key field

Re-enter the security key.

Suggest button

Suggests the security key or key ID that can be used.

Save button

Saves the data.

Cancel button

Cancels the action.

Step 5

Click Save.

Modifying Controller Security

Before you begin

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

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

In the Actions drop-down list on the right pane, click Storage > Modify Drive Security.

The Modify Drive Security dialog box appears.

Step 4

In the Modify Drive Security dialog box, review the following information:

Name Description

Controller Security field

Indicates whether or not controller security is enabled. This can be one of the following:

  • True— Controller security is enabled.

  • False— Controller security is disabled.

Security Key Identifier field

The current key ID.

Security Key field

Security key used to enable controller security. If you wish to change the current security key, enter the new key here.

Note

 

Once you change the security key, a Secure Key Verification pop-up window appears where you need to enter the current security key to verify it.

Confirm Security Key field

Re-enter the security key.

Suggest button

Suggests the security key or key ID that can be used.

Save button

Saves the data.

Cancel button

Cancels the action.

Step 5

Click Save.

Disabling Controller Security

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

In the Actions drop-down list on the right pane, click Storage > Disable Drive Security.

Click Yes or No at the prompt.

Switching Controller Security Between Local and Remote Key Management

This task allows you to switch controller security from local management to remote management, and from remote to local management.

Before you begin

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

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

In the Controller Info tab on the right pane, from the Actions drop-down list, select Switch to Local Key Management to switch the controller security from remote to local management.

Note

 
When you switch from remote to local key management, ensure that you disable KMIP secure key management first.

Step 4

(Optional) Similarly, if you want to switch the controller security from local to remote management, select Switch to Remote Key Management.

Step 5

Click OK to confirm.

Create Virtual Drive from Unused Physical Drives

Before you begin

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

This is available only on some C-series servers.


Note

Cisco IMC now supports single drive support in M.2 RAID controller along with existing dual drive support.

With single drive support, you cannot create a virtual disk.

SUMMARY STEPS

  1. From the Apps drop-down list, select Storage.
  2. From Storage > Controllers, click the appropriate LSI MegaRAID controller.
  3. On the right pane, click the Virtual Drive Info tab.
  4. From the Actions drop-down list on the right pane, click Storage > Create Virtual Drive.
  5. In the Select Controller
  6. In the Create / Carve VD page, enter the following information:
  7. In the RAID Type & PDs page, enter the following information:
  8. In the VD Properties page, enter the following information:
  9. In the Summary page, review the information and click Create.

DETAILED STEPS

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Virtual Drive Info tab.

Step 4

From the Actions drop-down list on the right pane, click Storage > Create Virtual Drive.

The Create Virtual Drive pane is displayed.

Step 5

In the Select Controller

Name

Description

MRAID drop-down list

Select the MRAID from the drop-down list and click Next.

Step 6

In the Create / Carve VD page, enter the following information:

Name

Description

From Unused Physical Drives radio button

Select this option to create a VD from unused physical drives

From Existing Drive Group radio button

Select this option to create a VD from existing groups.

Virtual Drive drop-down list

This option is available only with From Existing Drive Group.

Select the VD from the list and click Next.

Step 7

In the RAID Type & PDs page, enter the following information:

RAID Type

Table 1. RAID Type

Name

Description

RAID Type drop-down list

Select the RAID level for the new virtual drives. This can be one of the following:

  • Raid 0—Simple striping.

  • Raid 1—Simple mirroring.

  • Raid 5—Striping with parity.

  • Raid 6—Striping with two parity drives.

  • Raid 10—Spanned mirroring.

  • Raid 50—Spanned striping with parity.

  • Raid 60—Spanned striping with two parity drives.

  • Raid 00—Spanned striping.

Note

 

You must have multiple drive groups available to create virtual drives for certain RAID levels. While creating drives for these RAID levels, the create drive option is available only if the required number of drives are selected.

Physical Drives

Table 2. Physical Drives
Name Description

Physical Drives table

A list of physical drives that are not already included in a drive group.

ID column

The ID of the physical drive.

Size (GB) column

The size of the physical drive in MB.

Model column

The drive vendor name.

Interface Type column

Whether the drive is SAS or SATA

Type column

Type of the drive SSD or HDD.

> button

Adds the drive selected in the Physical Drives table to the drive group.

< button

Removes the drive selected in the Drive Groups table from the drive group.

Drives/Span table

A list of drive groups

Name column

The name of the drive group to be created.

Note

 

The size of the smallest physical drive in the drive group defines the maximum size used for all the physical drives. To ensure maximum use of space for all physical drives, it is recommended that the size of all the drives in the drive group are similar.

Step 8

In the VD Properties page, enter the following information:

Table 3. Virtual Drives in this group
Name Description

ID column

The ID of the virtual drive.

Name column

The name of the virtual drive.

Size (MB) column

The size of the virtual drive.

Step 9

In the Summary page, review the information and click Create.

Create Virtual Drive from an Existing Drive Group

Before you begin

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

SUMMARY STEPS

  1. From the Apps drop-down list, select Storage.
  2. From Storage > Controllers, click the appropriate LSI MegaRAID controller.
  3. On the right pane, click the Virtual Drive Info tab.
  4. From the Actions drop-down list on the right pane, click Storage > Create Virtual Drive.
  5. In the Select Controller
  6. In the Create / Carve VD page, enter the following information:
  7. In the RAID Type & PDs page, enter the following information:
  8. In the VD Properties page, enter the following information:
  9. In the Summary page, review the information and click Create.

DETAILED STEPS

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Virtual Drive Info tab.

Step 4

From the Actions drop-down list on the right pane, click Storage > Create Virtual Drive.

The Create Virtual Drive pane is displayed.

Step 5

In the Select Controller

Name

Description

MRAID drop-down list

Select the MRAID from the drop-down list and click Next.

Step 6

In the Create / Carve VD page, enter the following information:

Name

Description

From Unused Physical Drives radio button

Select this option to create a VD from unused physical drives

From Existing Drive Group radio button

Select this option to create a VD from existing groups.

Virtual Drive drop-down list

This option is available only with From Existing Drive Group.

Select the VD from the list and click Next.

Step 7

In the RAID Type & PDs page, enter the following information:

RAID Type

Table 4. RAID Type

Name

Description

RAID Type drop-down list

Select the RAID level for the new virtual drives. This can be one of the following:

  • Raid 0—Simple striping.

  • Raid 1—Simple mirroring.

  • Raid 5—Striping with parity.

  • Raid 6—Striping with two parity drives.

  • Raid 10—Spanned mirroring.

  • Raid 50—Spanned striping with parity.

  • Raid 60—Spanned striping with two parity drives.

  • Raid 00—Spanned striping.

Note

 

  • Configure RAID Type is available only when From Existing Drive Group is selected.

  • You must have multiple drive groups available to create virtual drives for certain RAID levels. While creating drives for these RAID levels, the Create Drive option is available only if the required number of drives are selected.

Physical Drives

Table 5. Physical Drives
Name Description

Physical Drives table

A list of physical drives that are not already included in a drive group.

ID column

The ID of the physical drive.

Size (GB) column

The size of the physical drive in MB.

Model column

The drive vendor name.

Interface Type column

Whether the drive is SAS or SATA

Type column

Type of the drive SSD or HDD.

> button

Adds the drive selected in the Physical Drives table to the drive group.

< button

Removes the drive selected in the Drive Groups table from the drive group.

Drives/Span table

A list of drive groups

Name column

The name of the drive group to be created.

Note

 

The size of the smallest physical drive in the drive group defines the maximum size used for all the physical drives. To ensure maximum use of space for all physical drives, it is recommended that the size of all the drives in the drive group are similar.

Size is available only when From Existing Drive Group is selected.

Table 6. Size

Name

Description

Size drop-down list

The size of the virtual drive you want to create.

Step 8

In the VD Properties page, enter the following information:

Table 7. Virtual Drives in this group
Name Description

ID column

The ID of the virtual drive.

Name column

The name of the virtual drive.

Size (MB) column

The size of the virtual drive.

Virtual Drives in this group is available only when From Existing Drive Group is selected.

Step 9

In the Summary page, review the information and click Create.

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

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Virtual Drive Info tab.

Step 4

In the Virtual Drives area, choose the drive and click Set Transport Ready.

The Set Transport Ready dialog box displays.

Step 5

Update the following properties in the dialog box:

Name Description

Initialize Type drop-down list

Allows you to select 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 Dedicated Hot Spare Drive— Includes exclusive dedicated hot spare drives.

Set Transport Ready button

Sets the selected virtual drive as transport ready.

Cancel button

Cancels the action.

Note

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

Importing Foreign Configuration

When a set of physical drives hosting a secured drive group are inserted into a different server or controller (or the same controller but whose security-key has been changed while they were not present), they become foreign configurations. Since they are secured, these foreign configurations must be unlocked by verifying their security key information before they can be imported.

Complete the following steps to verify the security key for a foreign configuration and import the configuration:

Before you begin

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

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the Storage tab, click the appropriate LSI MegaRAID controller.

Step 4

On the right pane, click the Controller Info tab.

Step 5

In the Actions drop-down list, click Storage > Import Foreign Config.

The Import Foreign Config window is displayed with the following message:

Are you sure you want import foreign config?

Click OK.

This action opens the Secure Key Verification dialog box. Review the following information before proceeding:

Table 8. Secure Key Verification Area

Name

Description

Security Key field

Unique key ID assigned to a controller.

Verify button

Verifies if the key you entered matches the stored key information.

If the secure key is verified to be correct, the requested action is completed.

Cancel button

Cancels the action.

Step 6

Click OK to confirm.

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.

SUMMARY STEPS

  1. From the Apps drop-down list, select Storage.
  2. From Storage > Controllers, click the appropriate LSI MegaRAID controller.
  3. On the Storage tab, click the appropriate LSI MegaRAID controller.
  4. On the right pane, click the Controller Info tab.
  5. In the Actions drop-down list on the right pane, click Storage > Clear Foreign Config.
  6. Click OK to confirm.

DETAILED STEPS

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the Storage tab, click the appropriate LSI MegaRAID controller.

Step 4

On the right pane, click the Controller Info tab.

Step 5

In the Actions drop-down list on the right pane, click Storage > Clear Foreign Config.

Step 6

Click OK to confirm.

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

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

In the Actions drop-down list on the right pane, click Storage > Clear Boot Drive.

Step 4

Click OK to confirm.

Enabling a JBOD


Note

You can enable Just a Bunch Of Disks (JBOD) only on some UCS C-Series servers.

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Controller Info tab.

Step 4

In the Actions drop-down list on the right pane, select Enable JBOD.

Step 5

Click OK to confirm.

Disabling a JBOD


Note

This option is available only on some UCS C-Series servers.

Before you begin

JBOD option must be enabled for the selected controller.

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Controller Info tab.

Step 4

In the Actions drop-down list on the right pane, click Disable JBOD.

Step 5

Click OK to confirm.

Retrieving TTY Logs for a Controller

This task retrieves the TTY 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

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Controller Info tab.

Step 4

In the Actions area, click Get TTY Log.

Step 5

Click OK to confirm.

Important

 

Retrieving TTY logs for a controller could take up to 2-4 minutes. Until this process is complete, do not initiate exporting technical support data.

Clearing Controller Configuration

Before you begin

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

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

In the Actions drop-down list on the right pane, click Storage > Clear All Configuration.

Step 4

Click OK to confirm.

This clears the existing controller configuration.

Restoring Storage Controller to Factory Defaults

Before you begin

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

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

In the Actions drop-down list on the right pane, click Storage > Set Factory Defaults.

Step 4

Click OK to confirm.

This restores the controller configuration to factory defaults.

Preparing a Drive for Removal


Note

You can perform 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.

SUMMARY STEPS

  1. From the Apps drop-down list, select Storage.
  2. From Storage > Controllers, click the appropriate LSI MegaRAID controller.
  3. On the right pane, click the Physical Drive Info tab.
  4. Select the drive you want to remove.
  5. Click the 3 horizontal dots near the selected drive and select Prepare for Removal from the drop-down list.
  6. Click OK to confirm.

DETAILED STEPS

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Physical Drive Info tab.

Step 4

Select the drive you want to remove.

Step 5

Click the 3 horizontal dots near the selected drive and select Prepare for Removal from the drop-down list.

Step 6

Click OK to confirm.

Making a Dedicated Hot Spare

Before you begin

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

SUMMARY STEPS

  1. From the Apps drop-down list, select Storage.
  2. From Storage > Controllers, click the appropriate LSI MegaRAID controller.
  3. On the right pane, click the Physical Drive Info tab.
  4. In the Physical Drive Info tab, select the physical drive you want to make a dedicated hot spare.
  5. Click the 3 horizontal dots and select Make Dedicated Hot Spare from the drop-down list.
  6. In the Virtual Drive Details area, update the following properties:
  7. Click Make Dedicated Hot Spare to confirm.

DETAILED STEPS

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Physical Drive Info tab.

Step 4

In the Physical Drive Info tab, select the physical drive you want to make a dedicated hot spare.

Step 5

Click the 3 horizontal dots and select Make Dedicated Hot Spare from the drop-down list.

The Make Dedicated Hot Spare dialog box displays.

Step 6

In the Virtual Drive Details area, update the following properties:

Name Description

Virtual Drive Number drop-down list

Select the virtual drive to which you want to dedicate the physical drive as hot spare.

Virtual Drive Name field

The name of the selected virtual drive.

Physical Drive Number field

The number of the physical drive.

Step 7

Click Make Dedicated Hot Spare to confirm.

Making a Global Hot Spare

Before you begin

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

SUMMARY STEPS

  1. From the Apps drop-down list, select Storage.
  2. From Storage > Controllers, click the appropriate LSI MegaRAID controller.
  3. On the right pane, click the Physical Drive Info tab.
  4. In the Physical Drive Info tab, select the physical drive you want to make a global hot spare.
  5. Click the 3 horizontal dots and select Make Global Hot Spare from the drop-down list.

DETAILED STEPS

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Physical Drive Info tab.

Step 4

In the Physical Drive Info tab, select the physical drive you want to make a global hot spare.

Step 5

Click the 3 horizontal dots and select Make Global Hot Spare from the drop-down list.

Removing a Drive from Hot Spare Pools

Before you begin

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

SUMMARY STEPS

  1. From the Apps drop-down list, select Storage.
  2. From Storage > Controllers, click the appropriate LSI MegaRAID controller.
  3. On the right pane, click the Physical Drive Info tab.
  4. In the Physical Drive Info tab, select the global or dedicated hot spare you want to remove from the hot spare pools.
  5. Click Remove From Hot Spare Pools.

DETAILED STEPS

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Physical Drive Info tab.

Step 4

In the Physical Drive Info tab, select the global or dedicated hot spare you want to remove from the hot spare pools.

Step 5

Click Remove From Hot Spare Pools.

Toggling Physical Drive Status

Before you begin

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

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Physical Drive Info tab.

Step 4

In the Physical Info tab, select the drive you want to set as unconfigured good.

Step 5

Click the three horizontal dots near the selected drive and click Set State as Unconfigured Good from the drop-down list.

Step 6

Click OK to confirm that the JBOD mode be disabled.

The Set State as JBOD option is enabled.

Step 7

To enable the JBOD mode for the physical drive, click Set State as JBOD.

Step 8

Click OK to confirm.

The Set State as Unconfigured Good option is enabled.

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

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Physical Drive Info tab.

Step 4

In the Physical Drive Info tab, select the drive you want to set as boot drive for the controller.

Step 5

Click the three horizontal dots near the selected drive and select Set as Boot Drive from the drop-down list.

Step 6

Click OK to confirm.

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.

SUMMARY STEPS

  1. From the Apps drop-down list, select Storage.
  2. From Storage > Controllers, click the appropriate LSI MegaRAID controller.
  3. On the right pane, click the Virtual Drive Info tab.
  4. In the Virtual Drive Info tab, choose the drive that you want to initialize.
  5. Click the 3 horizontal dots near the selected drive and click Initialize from the drop-down list.
  6. Choose the type of initialization you want to use for the virtual drive.
  7. Click Initialize VD to initialize the drive, or Cancel to close the dialog box without making any changes.
  8. To view the status of the task running on the drive, in the Operations area, click Refresh.

DETAILED STEPS

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Virtual Drive Info tab.

Step 4

In the Virtual Drive Info tab, choose the drive that you want to initialize.

Step 5

Click the 3 horizontal dots near the selected drive and click Initialize from the drop-down list.

The Initialize Virtual Drive dialog box displays.

Step 6

Choose the type of initialization you want to use for the virtual drive.

This can be one of the following:

  • Fast Initialize—This option allows you to start writing data to the virtual drive immediately.

  • Full Initialize—A complete initialization is done on the new configuration. You cannot write data to the new virtual drive until the initialization is complete.

Step 7

Click Initialize VD to initialize the drive, or Cancel to close the dialog box without making any changes.

Step 8

To view the status of the task running on the drive, in the Operations area, click Refresh.

The following details are displayed:

Name Description

Operation

Name of the operation that is in progress on the drive.

Progress in %

Progress of the operation, in percentage complete.

Elapsed Time in secs

The number of seconds that have elapsed since the operation began.

Set as Boot Drive

Before you begin

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

SUMMARY STEPS

  1. From the Apps drop-down list, select Storage.
  2. From Storage > Controllers, click the appropriate LSI MegaRAID controller.
  3. On the right pane, click the Physical Drive Info tab.
  4. In the Physical Drive Info tab, choose the drive from which the controller must boot.
  5. Click the 3 horizontal dots near the selected drive and click Set as Boot Drive.
  6. Click OK to confirm.

DETAILED STEPS

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Physical Drive Info tab.

Step 4

In the Physical Drive Info tab, choose the drive from which the controller must boot.

Step 5

Click the 3 horizontal dots near the selected drive and click Set as Boot Drive.

Step 6

Click OK to confirm.

Editing a Virtual Drive

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Virtual Drive Info tab.

Step 4

Click the 3 horizontal dots near the selected drive and click Edit Virtual Drive.

Step 5

Review the instructions, and then click OK.

The Edit Virtual Drive dialog box displays.

Step 6

From the Select RAID Level to migrate drop-down list, choose a RAID level.

See the following table for RAID migration criteria:

Name

Description

Select RAID Level to migrate drop-down list

Select the RAID level to which you want to migrate. Migrations are allowed for the following RAID levels:

  • RAID 0 to RAID 1

  • RAID 0 to RAID 5

  • RAID 0 to RAID 6

  • RAID 1 to RAID 0

  • RAID 1 to RAID 5

  • RAID 1 to RAID 6

  • RAID 5 to RAID 0

  • RAID 6 to RAID 0

  • RAID 6 to RAID 5

When you are migrating from one raid level to another, the data arms of the new RAID level should be equal to or greater than the existing one.

In case of RAID 6, the data arms will be number of drives minus two, as RAID 6 has double distributed parity. For example, when you create RAID 6 with eight drives, the number of data arms will be 8 – 2 = 6. In this case, if you are migrating from RAID 6 to RAID 0, RAID 0 must have a minimum of six drives. If you select lesser number of drives then Edit or Save button will be disabled.

If you are adding, you can migrate to RAID 0 as you will not be deleting any drives.

Note

 

RAID level migration is not supported in the following cases:

  • When there are multiple virtual drives in a RAID group.

  • With a combination of SSD/HDD RAID groups.

Step 7

From the Write Policy drop-down list in the Virtual Drive Properties area, choose one of the following:

  • Write Through— Data is written through the cache and to the physical drives. Performance is improved, because subsequent reads of that data can be satisfied from the cache.

  • Write Back— Data is stored in the cache, and is only written to the physical drives when space in the cache is needed. Virtual drives requesting this policy fall back to Write Through caching when the BBU cannot guarantee the safety of the cache in the event of a power failure.

  • Write Back Bad BBU—With this policy, write caching remains Write Back even if the battery backup unit is defective or discharged.

Step 8

Click Save Changes.

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.

SUMMARY STEPS

  1. From the Apps drop-down list, select Storage.
  2. From Storage > Controllers, click the appropriate LSI MegaRAID controller.
  3. On the right pane, click the Virtual Drive Info tab.
  4. In the Virtual Drive Info tab, select the virtual drive you want to delete.
  5. Click the 3 horizontal dots near the selected drive and click Delete Virtual Drive.
  6. Click OK to confirm.

DETAILED STEPS

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Virtual Drive Info tab.

Step 4

In the Virtual Drive Info tab, select the virtual drive you want to delete.

Step 5

Click the 3 horizontal dots near the selected drive and click Delete Virtual Drive.

Step 6

Click OK to confirm.

Hiding a Virtual Drive

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Virtual Drive Info tab.

Step 4

In the Virtual Drive Info tab, select the virtual drive you want to hide.

Step 5

Click the 3 horizontal dots near the selected drive and click Hide Drive.

Step 6

Click OK to confirm.

Starting Learn Cycles for a Battery Backup Unit

Before you begin

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

SUMMARY STEPS

  1. From the Apps drop-down list, select Storage.
  2. From Storage > Controllers, click the appropriate LSI MegaRAID controller.
  3. On the Storage tab, click the appropriate LSI MegaRAID controller.
  4. On the right pane, click the Battery Backup Unit tab.
  5. From the Actions pane, click Start Learn Cycle.
  6. Click OK.

DETAILED STEPS

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the Storage tab, click the appropriate LSI MegaRAID controller.

Step 4

On the right pane, click the Battery Backup Unit tab.

Step 5

From the Actions pane, click Start Learn Cycle.

A dialog prompts you to confirm the task.

Step 6

Click OK.

Viewing Storage Controller Logs

Before you begin

You must log in with admin privileges to perform this task

SUMMARY STEPS

  1. From the Apps drop-down list, select Storage.
  2. From Storage > Controllers, click the appropriate LSI MegaRAID controller.
  3. On the right pane, click Storage Log tab and review the following information:

DETAILED STEPS

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click Storage Log tab and review the following information:

Name

Description

Time column

The date and time the event occurred.

Severity column

The event severity. This can be one of the following:

  • Emergency

  • Alert

  • Critical

  • Error

  • Warning

  • Notice

  • Informational

  • Debug

Description column

A description of the event.

Viewing SSD Smart Information for MegaRAID Controllers

You can view smart information for a solid state drive.

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Physical Drive Info tab.

Step 4

Select the drive under the column Slot ID.

A new pane is displayed with the drive details.

Step 5

Click the Details tab and review the following information:

Table 9. Product Details

Name

Description

Power Cycle Count

Number of power cycles that the drive went through from the time it was manufactured.

Power on Hours

Total number of hours that the drive is in the 'Power On' mode.

Percentage Life Left

The number of write cycles remaining in a solid state drive (SSD). For instance, if an SSD is capable of 100 write cycles during its life time, and it has completed 15 writes, then the percentage of life left in the drive is 85%. Each percentage range is represented in a different color. For instance, green for 75% to 100% and red for 1 to 25%.

Wear Status in Days

The number of days an SSD has gone through with the write cycles.

SSD vendors provide a finite number of writes per day on the SSD, based on which, you can calculate the total number of years the SSD would continue to work.

Operating Temperature

The current temperature of the drive at which the selected SSD operates at the time of selection.

Maximum Operating Temperature

Allowable maximum temperature in which the drive can operate without errors.

Percentage Reserved Capacity Consumed

The total capacity (out of the percentage reserved for it) consumed by the drive.

Step 6

Click Close.

Viewing NVMe Controller Details

Before you begin

  • The server must be powered on.

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate NVMe controller.

Step 3

In the Controller Info tab on the right pane, review the following information under the General tab.

Name

Description

Product Name

The name of the MegaRAID controller.

Product ID

Cisco part number of the RAID controller.

Composite Health

The combined health of the controller, the attached drives, and the battery backup unit. This can be one of the following:

  • Good

  • Moderate Fault

  • Severe Fault

  • N/A

Controller Status

The current status of the controller. This can be one of the following:

  • Optimal — The controller is functioning properly.

  • Failed — The controller is not functioning.

  • Unresponsive — The controller is down.

Security

Displays the controller lock key depending on its current state.

Note

 

  • This option is available only on some C-Series servers.

  • Disabling the drive security makes the data on all secure drives unusable.

Serial Number field

The serial number of the MegaRAID controller.

RAID Chip Temperature field

Temperature of the controller in degree centigrade.

Firmware Package Build field

The active firmware package version number.

For the firmware component version numbers, see the Running Firmware Images area.

Consistency Check Rate field

The rate at which the controller scans the virtual drives looking for redundant data inconsistencies and fixing them.

This rate is shown as a percentage of the total bandwidth available.

PCI Slot

The name of the PCIe slot in which the controller is located.

Vendor ID

The PCI vendor ID, in hexadecimal.

SubVendor ID

The PCI subvendor ID, in hexadecimal.

Device ID

The PCI device ID, in hexadecimal.

Sub Device ID

The PCI subdevice ID, in hexadecimal.

Manufactured Date

The date the MegaRAID card was manufactured, in the format yyy-mm-dd.

Revision

The board revision number, if any.

Boot Drive(s)

The number of the boot drive.

Interface Type

Whether the drive is SAS or SATA

Viewing NVMe Physical Drive Details

Before you begin

  • The server must be powered on.

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate NVMe controller.

Step 3

Click the Physical Drive Info tab on the right pane and review the following information:

Name

Description

Slot ID

The name of the PCIe slot in which the controller drive is located.

Disk Type

Whether the drive is a hard drive (HDD) or a solid state drive (SSD).

Status

The physical drive status. This can be one of the following:

  • Copyback—The drive is busy performing a copyback operation.

  • Failed—The drive was in use, but it has failed.

  • Foreign configuration—The drive contains a foreign configuration.

  • Global hot spare—The drive is designated as a global spare drive.

  • Dedicated hot spare—The drive is designated as a dedicated spare drive.

  • Offline—The drive is offline and cannot be accessed.

  • Online—The drive is in use as part of a drive group.

  • Predicted Failure—The drive is marked as due to fail soon by the controller.

  • Ready to remove—The drive is prepared for removal.

  • Rebuild—The drive is currently being rebuilt.

  • System—The drive is visible to the host and cannot be used for virtual drives.

  • Unconfigured bad—The drive has failed and is not in use.

  • Unconfigured good—The drive is ready to be assigned to a drive group or hot spare pool.

Capacity (GB)

The capacity of the drive in gigabytes.

Model

The drive vendor name.

Firmware

The firmware version running on the drive.

Step 4

Select a drive under the column Slot ID.

A new pane is displayed with the drive details.

View the drive details in the General tab.

Table 10. General Tab

Name

Description

Media Type

Whether the drive is a hard drive (HDD) or a solid state drive (SSD).

Interface Type

The drive interface type.

Sequence Number

The sequence number used by the controller to track drive changes.

Security Enabled

If this field displays Yes, full disk encryption is enabled on the physical drive.

Physical Block Size

Indicates the physical block size of the drive.

Slot Number

The slot number in which the physical drive resides.

Device ID

The device ID for the drive.

Product ID

The drive product ID. This field generally displays the drive model number.

UCS Product ID

Vendor

The vendor for the drive.

Drive Firmware

The active firmware version on the drive.

Drive Serial Number

The serial number for the drive.

Raw Size

The capacity of drive in megabytes, including the space used for formatting.

Non Coerced Size

The capacity in megabytes, including space lost to coercion.

Coerced Size

The capacity in megabytes after any coercion rounding has been performed.

Negotiated Link Speed

The speed of the link between the drive and the controller.

Viewing PCI Switch Details

Before you begin

The server must be powered on, or the properties will not display.

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate PCI Switch controller.

Step 3

Review the following information:

General Tab

Name

Description

Product Name

The name of the MegaRAID controller.

Product ID

Cisco part number of the RAID controller.

Composite Health

The combined health of the controller, the attached drives, and the battery backup unit. This can be one of the following:

  • Good

  • Moderate Fault

  • Severe Fault

  • N/A

Controller Status

The current status of the controller. This can be one of the following:

  • Optimal — The controller is functioning properly.

  • Failed — The controller is not functioning.

  • Unresponsive — The controller is down.

Security

Displays the controller lock key depending on its current state.

Note

 

  • This option is available only on some C-Series servers.

  • Disabling the drive security makes the data on all secure drives unusable.

Serial Number field

The serial number of the MegaRAID controller.

RAID Chip Temperature field

Temperature of the controller in degree centigrade.

Firmware Package Build field

The active firmware package version number.

For the firmware component version numbers, see the Running Firmware Images area.

Consistency Check Rate field

The rate at which the controller scans the virtual drives looking for redundant data inconsistencies and fixing them.

This rate is shown as a percentage of the total bandwidth available.

PCI Slot

The name of the PCIe slot in which the controller is located.

Vendor ID

The PCI vendor ID, in hexadecimal.

SubVendor ID

The PCI subvendor ID, in hexadecimal.

Device ID

The PCI device ID, in hexadecimal.

Sub Device ID

The PCI subdevice ID, in hexadecimal.

Manufactured Date

The date the MegaRAID card was manufactured, in the format yyy-mm-dd.

Revision

The board revision number, if any.

Boot Drive(s)

The number of the boot drive.

Interface Type

Whether the drive is SAS or SATA
Settings Area
Table 11. Settings Area

Name

Description

Physical Drive Status Auto Config Mode

The physical drive status auto config mode that you select for the controller. This can be one of the following:

  • Unconfigured Good - The default option. Select this option if you are using the server for RAID volume and mixed JBOD.

  • RAID-0 Write Back - Select this option if you are using the server for per drive R0 WB.

  • JBOD - Select this option if you are using the server for JBOD only.

Rebuild Rate

The rate at which the controller rebuilds degraded RAID volumes.

This rate is shown as a percentage of the total bandwidth available.

Patrol Read Rate

The rate at which the controller performs a background read of the physical drives looking for inconsistent data.

This rate is shown as a percentage of the total bandwidth available.

Consistency Check Rate

The rate at which the controller scans the virtual drives looking for redundant data inconsistencies and fixing them.

This rate is shown as a percentage of the total bandwidth available.

ECC Bucket Leak Rate

The error correcting code (ECC) single-bit error bucket leak rate, in minutes.

With ECC, the controller increments an error counter when it encounters a single bit error while reading from a physical drive. The controller decrements the error counter each time the number of minutes defined in this field passes.

If the error counter reaches a system-defined maximum, the controller sends an event message to the system.

JBOD

If this field displays true, JBOD is enabled.

Maintain PD Fail History

If this field displays true, the controller remembers which physical drives were determined to be bad across server reboots.

Battery Warning

If this field displays true, missing battery warnings are disabled.

Table 12. HW Config Area

Name

Description

Controller SAS Address

A MegaRAID controller can have up to 16 serial-attached SCSI (SAS) addresses. This field displays the first 8 SAS addresses, if they are in use.

BBU Present

If this field displays true, the battery backup unit is present.

Memory Present

If this field displays true, memory is present.

Flash Present

If this field displays true, flash memory is present.

Table 13. Capabilities Area

Name

Description

RAID Levels Supported

The RAID levels supported by the controller. This can be one or more of the following:

  • Raid 0—Simple striping.

  • Raid 1—Simple mirroring.

  • Raid 5—Striping with parity.

  • Raid 1E—Integrated offset strip mirroring

  • Raid 6—Striping with two parity drives.

  • Raid 10—Spanned mirroring.

  • Raid 50—Spanned striping with parity.

  • Raid 60—Spanned striping with two parity drives.

  • Raid srl-03—Spanned secondary RAID level

  • Raid 00—Spanned striping.

  • Raid 1e-rlq0—Integrated adjacent strip mirroring with no span.

  • Raid 1e0-rlq0—Integrated adjacent strip mirroring with span.
Table 14. Error Counters Area

Name

Description

Memory Correctable Errors

The number of correctable errors in the controller memory.

Starting Copyback Operation

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID or HBA controller.

Step 3

Click the Physical Drive Info tab on the right pane and select a drive, which is in online state.

Step 4

In the Actions drop-down list, click Start Copyback.

Step 5

A Start Copyback Operation dialog box is displayed.

Step 6

Select the Destination Physical Drive to which the copyback operation needs to be done.

Step 7

Click Start Copyback.

Step 8

You can also perform the following copyback operations:

  • Pause Copyback - If the drive is in copyback state, you can pause the copyback operation.

  • Resume Copyback- The paused copyback operation can be resumed.

  • Abort Copyback - If the drive is in copyback state, you can abort the copyback operation.

Managing the Flexible Flash Controller

Cisco Flexible Flash

On the M5 servers, Flexible Flash Controller is inserted into the mini storage module socket. The mini storage socket is inserted into the M.2 slot on the motherboard. M.2 slot also supports SATA M.2 SSD slots.


Note

M.2 slot does not support NVMe in this release.

Some C-Series Rack-Mount Servers support an internal Secure Digital (SD) memory card for storage of server software tools and utilities. The SD card is hosted by the Cisco Flexible Flash storage adapter.

The SD storage is available to Cisco IMC as a single hypervisor (HV) partition configuration. Prior versions had four virtual USB drives. Three were preloaded with Cisco UCS Server Configuration Utility, Cisco drivers and Cisco Host Upgrade Utility, and the fourth as user-installed hypervisor. A single HV partition configuration is also created when you upgrade to the latest version of Cisco IMC or downgrade to the prior version, and reset the configuration.

For more information about installing and configuring the M.2 drives, see the Storage Controller Considerations (Embbeded SATA RAID Requirements) and Replacing an M.2 SSD in a Mini-Storage Carrier For M.2 sections in the Cisco UCS Server Installation and Service Guide for the C240 M5 servers at this URL:

https://www.cisco.com/c/en/us/support/servers-unified-computing/ucs-c-series-rack-servers/products-installation-guides-list.html

For information about the Cisco software utilities and packages, see the Cisco UCS C-Series Servers Documentation Roadmap at this URL:

http://www.cisco.com/go/unifiedcomputing/c-series-doc

Card Management Feature in the Cisco Flexible Flash Controller

The Cisco Flexible Flash controller supports management of both single and two SD cards as a RAID-1 pair. With the introduction of card management, you can perform the following tasks:


Note

  • If you want to upgrade from version 1.4(5e) to 1.5(4) or higher versions, you must first upgrade to version1.5(2) and then upgrade to a higher version of Cisco IMC.

  • Reset the Cisco Flexible Flash controller to load the latest Flex Flash firmware after every Cisco IMC firmware upgrade.

Action

Description

Reset Cisco Flex Flash

Allows you to reset the controller.

Reset Partition Defaults

Allows you to reset the configuration in the selected slot to the default configuration.

Synchronize Card Configuration

Allows you to retain the configuration for an SD card that supports firmware version 253 and later.

Configure Operational Profile

Allows you to configure the SD cards on the selected Cisco Flexible Flash controller.

RAID Partition Enumeration

Non-RAID partitions are always enumerated from the primary card and the enumeration does not depend on the status of the primary card.

Following is the behavior of the RAID partition enumeration when there are two cards in the Cisco Flexible Flash controller:

Scenario Behavior

Single card

RAID partitions are enumerated if the card is healthy, and if the mode is either Primary or Secondary-active.

Dual paired cards

RAID partitions are enumerated if one of the cards is healthy.

When only one card is healthy, all read/write operations occur on this healthy card. You must use UCS SCU to synchronize the two RAID partitions.

Dual unpaired cards

If this scenario is detected when the server is restarting, then neither one of the RAID partitions is enumerated.

If this scenario is detected when the server is running, when a user connects a new SD card, then the cards are not managed by the Cisco Flexible Flash controller. This does not affect the host enumeration. You must pair the cards to manage them. You can pair the cards using the Reset Partition Defaults or Synchronize Card Configuration options.

Upgrading from Single Card to Dual Card Mirroring with FlexFlash

You can upgrade from a single card mirroring to dual card mirroring with FlexFlash in one of the following methods:

  • Add an empty FlexFlash card to the server, and then upgrade its firmware to the latest version.

  • Upgrade the FlexFlash firmware to the latest version and then add an empty card to the server.

Prior to using either of these methods, you must keep in mind the following guidelines:

  • To create RAID1 mirroring, the empty card that you want to add to the server must be of the exact size of the card that is already in the server. Identical card size is a must to set up RAID1 mirroring.

  • Ensure that the card with valid data in the Hypervisor partition is marked as the primary healthy card. You can determine this state either in the Cisco IMC GUI or from the Cisco IMC CLI. To mark the state of the card as primary healthy, you can either use the Reset Configuration option in the Cisco IMC GUI or run the reset-config command in the CLI. When you reset the configuration of a particular card, the secondary card is marked as secondary active unhealthy.

  • In a Degraded RAID health state all read-write transactions are done on the healthy card. In this scenario, data mirroring does not occur. Data mirroring occurs only in the Healthy RAID state.

  • Data mirroring is only applicable to RAID partitions. In the C-series servers, only Hypervisor partitions operate in the RAID mode.

  • If you have not configured SD cards for use with prior versions, then upgrading to the latest version loads the latest 253 firmware and enumerates all four partitions to the host.

While upgrading versions of the FlexFlash, you may see the following error message:

Unable to communicate with Flexible Flash controller: operation ffCardsGet, status CY_AS_ERROR_INVALID_RESPONSE”

In addition, the card status may be shown as missing. This error occurs because you accidently switched to an alternate release or a prior version, such as 1.4(x). In this scenario, you can either revert to the latest Cisco IMC version, or you can switch back to the FlexFlash 1.4(x) configuration. If you choose to revert to the latest version, then the Cisco FlexFlash configuration remains intact. If you choose to switch back to the prior version configuration, you must reset the Flexflash configuration. In this scenario, you must be aware of the following:

  • If multiple cards are present, and you revert to a prior version, then the second card cannot be discovered or managed.

  • If the card type is SD253, then you must run the reset-config command twice from the Cisco IMC CLI - once to reload the old firmware on the controller and to migrate SD253 to SD247 type, and the second time to start the enumeration.

Configuring the Flexible Flash Controller Properties

After you upgrade to the latest verison of Cisco IMC or downgrade to a prior version, and reset the configuration, the server will access HV partition only.

Before you begin

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

  • Cisco Flexible Flash must be supported by your platform.


Note

This task results in the host re-scanning all the virtual drives, and a loss of virtual drive connectivity. We recommend that you configure the controller properties before using any virtual drives, or power down the host prior to starting this task

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

On the Storage > Cisco FlexFlash.

Step 3

In the Controller Info tab on the right pane, click Configure Operational Profile.

Step 4

In the Operational Profile dialog box, update the following fields:

Table 15. Operational Profile Fields for Cisco UCS M5 Servers
Name Description

Controller field

The system-defined name of the selected Cisco Flexible Flash controller.

This name cannot be changed.

Firmware Operating Mode field

System displayed message. Displays the firmware operating mode as Mirror.

SLOT-1 Read Error Threshold field

The number of read errors that are permitted while accessing Slot 1 of the Cisco Flexible Flash card. If the number of read errors exceeds this threshold on a card, the card is marked unhealthy.

To specify a read error threshold, enter an integer between 1 and 255. To specify that the card should never be disabled regardless of the number of errors encountered, enter 0 (zero).

SLOT-1 Write Error Threshold field

The number of write errors that are permitted while accessing Slot 1 of the Cisco FlexFlash card. If the number of write errors exceeds this threshold on a card, the card is marked unhealthy.

To specify a write error threshold, enter an integer between 1 and 255. To specify that the card should never be disabled regardless of the number of errors encountered, enter 0 (zero).

Step 5

Click Save.

Configuring the Flexible Flash Controller Firmware Mode

Before you begin

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

  • Cisco Flexible Flash must be supported by your platform.


Note

This task results in the host re-scanning all the virtual drives, and a loss of virtual drive connectivity. We recommend that you configure the Cisco Flexible Flash controller properties before using any virtual drives, or power down the host prior to starting this task.

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate Cisco Flexible Flash controller.

Step 3

In the Actions drop-down list, click Configure Firmware Mode.

Step 4

Click OK in the confirmation box.

Switches the controller firmware mode from the current firmware mode to the other.

Configuring the Flexible Flash Controller Cards

Before you begin

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

  • Cisco Flexible Flash must be supported by your platform.


Note

This task results in the host re-scanning all the virtual drives, and a loss of virtual drive connectivity. We recommend that you configure the Cisco Flexible Flash controller properties before using any virtual drives, or power down the host prior to starting this task.

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click Cisco FlexFlash.

Step 3

In the Actions drop-down list, click Configure Cards.

Configure Cards dialog box appears.

Step 4

In the Configure Cards dialog box, update the following fields:

Name Description

Mode field

Displays the mode type as Mirror.

Mirror Partition Name field

The name that you want to assign to the partition.

Auto Sync checkbox

If selected, data from the selected primary card syncs automatically with the secondary card.

Note

 

  • There must be two cards for you to choose this option.

  • If this option is selected, data on the secondary card is erased and overwritten by the data on the primary card.

  • The status of this is displayed under the Virtual Drive tab.

Select Primary Card drop-down

Slot that you want to set as the primary card. This can be one of the following:

  • Slot1

  • Slot2

Virtual Drive drop-down

The virtual drive type. This can be one of the following:

  • Removable

  • Non Removable

Step 5

Click Save.

The cards are configured in the chosen mode.

Booting from the Flexible Flash Card

You can specify a bootable virtual drive on the card that overrides the default boot priority the next time that the server is restarted, regardless of the default boot order defined for the server. The specified boot device is used only once. After the server has rebooted, this setting is ignored. You can choose a bootable virtual drive only if a card is available. Otherwise, the server uses a default boot order.


Note

Before you reboot the server, ensure that the virtual drive that you select is enabled on the card. Go to the Storage tab, choose the card, and then go to the Virtual Drive Info subtab.

Before you begin

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

  • Cisco Flexible Flash must be supported by your platform.

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click FlexFlash.

Step 3

In the Actions drop-down list on the right pane, click Configure Boot Override Priority.

The Boot Override Priority dialog box appears.

Step 4

From the Boot Override Priority drop-down list, choose a virtual drive to boot from.

Step 5

Click Apply.

Resetting the Flexible Flash Controller

In normal operation, it should not be necessary to reset the Cisco Flexible Flash. We recommend that you perform this procedure only when explicitly directed to do so by a technical support representative.


Note

This operation will disrupt traffic to the virtual drives on the Cisco Flexible Flash controller.

Before you begin

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

  • Cisco Flexible Flash must be supported by your platform.

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate Cisco FlexFlash controller.

Step 3

In the Cisco FlexFlash pane, click the Controller Info tab.

Step 4

In the Actions drop-down list on the right pane, click Reset FlexFlash Controller.

Step 5

Click OK to confirm.

Editing a Virtual Drive

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate LSI MegaRAID controller.

Step 3

On the right pane, click the Virtual Drive Info tab.

Step 4

Click the 3 horizontal dots near the selected drive and click Edit Virtual Drive.

Step 5

Review the instructions, and then click OK.

The Edit Virtual Drive dialog box displays.

Step 6

From the Select RAID Level to migrate drop-down list, choose a RAID level.

See the following table for RAID migration criteria:

Name

Description

Select RAID Level to migrate drop-down list

Select the RAID level to which you want to migrate. Migrations are allowed for the following RAID levels:

  • RAID 0 to RAID 1

  • RAID 0 to RAID 5

  • RAID 0 to RAID 6

  • RAID 1 to RAID 0

  • RAID 1 to RAID 5

  • RAID 1 to RAID 6

  • RAID 5 to RAID 0

  • RAID 6 to RAID 0

  • RAID 6 to RAID 5

When you are migrating from one raid level to another, the data arms of the new RAID level should be equal to or greater than the existing one.

In case of RAID 6, the data arms will be number of drives minus two, as RAID 6 has double distributed parity. For example, when you create RAID 6 with eight drives, the number of data arms will be 8 – 2 = 6. In this case, if you are migrating from RAID 6 to RAID 0, RAID 0 must have a minimum of six drives. If you select lesser number of drives then Edit or Save button will be disabled.

If you are adding, you can migrate to RAID 0 as you will not be deleting any drives.

Note

 

RAID level migration is not supported in the following cases:

  • When there are multiple virtual drives in a RAID group.

  • With a combination of SSD/HDD RAID groups.

Step 7

From the Write Policy drop-down list in the Virtual Drive Properties area, choose one of the following:

  • Write Through— Data is written through the cache and to the physical drives. Performance is improved, because subsequent reads of that data can be satisfied from the cache.

  • Write Back— Data is stored in the cache, and is only written to the physical drives when space in the cache is needed. Virtual drives requesting this policy fall back to Write Through caching when the BBU cannot guarantee the safety of the cache in the event of a power failure.

  • Write Back Bad BBU—With this policy, write caching remains Write Back even if the battery backup unit is defective or discharged.

Step 8

Click Save Changes.

Erasing Virtual Drives

Before you begin

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

  • Cisco Flexible Flash must be supported by your platform.


Note

This task results in the host re-scanning all the virtual drives, and a loss of virtual drive connectivity. We recommend that you configure the Cisco Flexible Flash controller properties before using any virtual drives.

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate Cisco FlexFlash controller.

Step 3

Click the Virtual Drive Info tab.

Step 4

In the Virtual Drive Info tab, click Erase Virtual Drive(s).

Step 5

In the Erase Virtual Drive(s) dialog box, select the virtual drives that you want to erase.

Step 6

Click Save.

Data on the selected virtual drives is erased.

Syncing Virtual Drives

Before you begin

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

  • Cisco Flexible Flash must be supported by your platform.

  • Cards must be in mirror mode.


Note

This task results in the host re-scanning all the virtual drives, and a loss of virtual drive connectivity. We recommend that you configure the Cisco Flexible Flash controller properties before using any virtual drives.

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate Cisco FlexFlash controller.

Step 3

Click the Virtual Drive Info tab.

Step 4

In the Virtual Drive Info tab, click Sync Virtual Drive.

Step 5

Click OK in the confirmation dialog box.

Syncs the virtual drive hypervisor with the primary card.

Adding an ISO Image Configuration

Before you begin

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

  • Cisco Flexible Flash must be supported by your platform.

  • The cards must be configured in Util mode.


Note

This task results in the host re-scanning all the virtual drives, and a loss of virtual drive connectivity. We recommend that you configure the Cisco Flexible Flash controller properties before using any virtual drives, or power down the host prior to starting this task.

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate Cisco Flexible Flash controller.

Step 3

Click the Virtual Drive Info tab.

Step 4

In the Virtual Drive Info tab, select the virtual drive for which you want to add an image.

Step 5

Click Add Image.

Step 6

In the Add Image dialog box, update the following fields:

Name Description

Volume field

The identity of the image mounted for mapping. This can be one of the following:

  • SCU

  • HUU

  • Drivers

Mount Type drop-down list

The type of mapping. This can be one of the following:

  • NFS—Network File System.

  • CIFS—Common Internet File System.

Remote Share field

The URL of the image to be mapped. The format depends on the selected Mount Type:

  • NFS—Use serverip:/share path.

  • CIFS—Use //serverip/share path.

Remote File field

The name and location of the .iso file in the remote share. Following are the example of remote share files:

  • NFS — /softwares/ucs-cxx-scu-3.1.9.iso

  • CIFS — /softwares/ucs-cxx-scu-3.1.9.iso

Mount Options field

Industry-standard mount options entered in a comma separated list. The options vary depending on the selected Mount Type.

If you are using NFS, leave the field blank or enter one or more of the following:

  • ro

  • rw

  • nolock

  • noexec

  • soft

  • port=VALUE

  • timeo=VALUE

  • retry=VALUE

If you are using CIFS, leave the field blank or enter one or more of the following:

  • soft

  • nounix

  • noserverino

User Name field

The username for the specified Mount Type, if required.

Password field

The password for the selected username, if required.

Step 7

Click Save.

Updating an ISO Image

Before you begin

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

  • Cisco Flexible Flash must be supported by your platform.

  • This task is available only when the cards are configured in Util mode.


Note

This task results in the host re-scanning all the virtual drives, and a loss of virtual drive connectivity. We recommend that you configure the Cisco Flexible Flash controller properties before using any virtual drives, or power down the host prior to starting this task.

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate Cisco Flexible Flash controller.

Step 3

Click the Virtual Drive Info tab.

Step 4

In the Virtual Drive Info tab, select the virtual drive on which you want to update the image, click Update Image.

Note

 

SCU and HUU update may take up to an hour and the drivers update may take up to five hours.

Unmapping an ISO Image

Before you begin

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

  • Cisco Flexible Flash must be supported by your platform.


Note

This task results in the host re-scanning all the virtual drives, and a loss of virtual drive connectivity. We recommend that you configure the Cisco Flexible Flash controller properties before using any virtual drives, or power down the host prior to starting this task.

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate Cisco Flexible Flash controller.

Step 3

Click the Virtual Drive Info tab.

Step 4

In the Virtual Drive Info tab, select the virtual drive for which you want to un map the image, click Unmap Image.

Resetting the Cisco Flexible Flash Card Configuration

When you reset the configuration of the slots in the Cisco Flexible Flash card, the following situations occur:

  • The card in the selected slot is marked as primary healthy.

  • The card in the other slot is marked as secondary-active unhealthy.

  • One RAID partition is created.

  • The card read/write error counts and read/write threshold are set to 0.

  • Host connectivity could be disrupted.

If you upgrade to the latest version and select reset configuration option, a single hypervisor (HV) partition is created, and the existing four partition configurations are erased. This may also result in data loss. You can retrieve the lost data only if you have not done any data writes into HV partition, and downgrade to prior version.

Before you begin

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

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate Cisco Flexible Flash controller.

Step 3

Click the Controller Info tab.

Step 4

In the Actions drop-down list on the right pane, click Reset Partition Defaults.

Step 5

In the Reset Partition Defaults dialog box, update the following fields:

Name Description

Slot radio button

Select the slot for which you want to mark the card as primary healthy.

The card in the other slot, if any, is marked as secondary-active unhealthy.

Reset Partition Defaults button

Resets the configuration of the selected slot.

Cancel button

Closes the dialog box without making any changes.

Step 6

Click Yes.

Retaining Configuration of the Cisco Flexible Flash Cards

You can retain the configuration for an FlexFlash that supports firmware version 253 and later card in the following situations:

  • There are two unpaired Cisco Flexible Flash cards.

  • The server is operating from a single FlexFlash, and an unpaired FlexFlash is in the other slot.

  • One FlexFlash supports firmware version 253, and the other FlexFlash is unpartitioned.

When you retain the configuration, the following situations occur:

  • The configuration for the FlexFlash in the selected slot is copied to the other card.

  • The card in the selected slot is marked as primary healthy.

  • The card in the secondary slot is marked as secondary-active unhealthy.

Before you begin

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

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate Cisco Flexible Flash controller.

Step 3

Click the Controller Info tab.

Step 4

In the Actions drop-down list on the right pane, click Synchronize Card Configuration.

Step 5

In the Synchronize Card Configuration dialog box, update the following fields:

Name Description

Slot radio button

Select the slot for which you want the configuration retained. The configuration is copied from the selected slot to the card in the other slot, and the card in the selected slot is marked as primary healthy.

Synchronize Card Configuration button

Copies the configuration from the selected card only if the selected card is of type SD253 and has single HV configuration.

Cancel button

Closes the dialog box without making any changes.

Step 6

Click Yes.

Viewing FlexFlash Log Details

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate Cisco Flexible Flash controller.

Step 3

In the FlexFlash Logs tab > FlexFlash LogTable area, review the following fields:

Name

Description

Time column

The date and time the event occurred.

Severity column

The event severity. This can be one of the following:

  • Emergency

  • Alert

  • Critical

  • Error

  • Warning

  • Info

  • Notice

  • Debug

Description column

A description of the event.

Step 4

In the FlexFlash Logs tab > Actions area, review the following fields:

Name

Description

Show drop-down list

Customize the way you want to view Cisco IMC log entries using filters. These can be:

  • Quick Filter— Default view

  • Advanced Filter— Filter options to display the log entries based on one or more criteria. Using the matching rule, you can view entries matching all the rules or any one combination of rules you specified in the Filter fields.

    Click + to add new filtering criteria.

    Click Go to view the entries matching the filter criteria that you set.

    Click the Save icon to save the filter criteria that you set. This becomes a user-defined filter which you can use later.

    Note

     

    The user-defined filter appears in the Manage Preset Filters dialog box.

  • All—Displays all entries

  • Manage Preset Filters—Displays user-defined filters. You can edit or remove the user-defined filter from this dialog box.

  • List of pre-defined filters— Displays the system-defined filters.

Filter icon

Displays or hides the quick filter fields.

Column drop-down list

Allows you to choose the columns you want to view.

Step 5

In the FlexFlash Logs tab > Log Navigation Toolbar area, review the following fields:

Name Description

<<Newest

If there are more events than can fit on a single page, click this link to view the newest entries.

The total number of entries displayed depends on the setting in the Entries per Page drop-down list.

<Newer

If there are more events than can fit on a single page, click this link to view the next page of entries that are newer than the set you are currently viewing.

Log Entries field

This field displays which log entries are currently being shown in the table.

Older>

If there are more events than can fit on a single page, click this link to view the next page of entries that are older than the set you are currently viewing.

Oldest>>

If there are more events than can fit on a single page, click this link to view the oldest entries.

Page Number drop-down list

Allows you to navigate to a specific page. Select the page number from the drop-down list.

Number of Rows field

Displays the rows displayed in the current page.

Managing the FlexUtil Controller

The Cisco UCS M5 servers support microSD memory card for storage of server software tools and utilities. Riser 1 has this microSD memory card slot. Cisco FlexUtil supports only 32GB microSD card.

The following user visible partitions are present on the microSD card:

  • Server Configuration Utility (SCU) – 1.25 GB

  • Diagnostics – 0.25 GB

  • Host Update Utility (HUU) – 1.5 GB

  • Drivers – 8 GB

  • User


Note
The number of partitions and size of each partition on microSD is fixed.

At any time, two partitions can be mapped onto the host. These partitions (except the user partition ) can also be updated through a CIFS or NFS share. A second level BIOS boot order support is also available for all the bootable partitions.


Note

User partition must be used only for storage. This partition does not support OS installations.

Configuring FlexUtil Controller Properties

Before you begin

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

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate Cisco FlexUtil controller.

Step 3

In the General tab > Actions area, click Configure Operational Profile.

Step 4

In the Operational Profile dialog box, update the following fields.

Name Description

Controller field

The system-defined name of the selected Flex Util controller.

This name cannot be changed.

Read Error Threshold field

The number of read errors that are permitted while accessing the Flex Util card. If the number of read errors exceeds this threshold on a card, the card is marked unhealthy.

To specify a read error threshold, enter an integer between 1 and 255. To specify that the card should never be disabled regardless of the number of errors encountered, enter 0 (zero).

Write Error Threshold field

The number of write errors that are permitted while accessing the Flex Util card. If the number of write errors exceeds this threshold on a card, the card is marked unhealthy.

To specify a write error threshold, enter an integer between 1 and 255. To specify that the card should never be disabled regardless of the number of errors encountered, enter 0 (zero).

Resetting FlexUtil Card Configuration

Before you begin

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

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate FlexUtil controller.

Step 3

In the General tab > Actions area, click Reset Card Configuration.

This action resets the FlexUtil card configuration to its default settings.

Viewing Cisco FlexUtil Controller Properties

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate FlexUtil controller.

Step 3

In the General tab > General area, review the following fields:

Name

Description

Product Name field

The name of the product.

Controller Name field

The name for the controller.

Controller Status field

The current status of the FlexUtil card. This can be one of the following:

  • Card is absent

  • Card is Unhealthy

  • Metadata Read Error

  • Card access error

  • Invalid Card size

  • Metadata is in failed state

  • No partition, reset required

  • Invalid partition, reset required

  • Card is write protected

Internal State field

The internal state of the controller. This can be one of the following:

  • Uninitialized—FlexUtil monitoring is not initialized.

  • Initializing—FlexUtil monitoring is initializing.

  • Configuring—The controller is determining the FlexUtil card configuration.

  • OK—The FlexUtil card is not connected to the host.

  • Connecting—The controller is connecting to the host.

  • Connected—The controller is connected to the host.

  • Failed—The controller has failed. See the Controller Status field for more details.

  • Erasing—The FlexUtil card is being erased.

  • Updating—The FlexUtil card is being updated.

  • Resetting—The configuration on the card is reset.

Step 4

In the General tab's Physical Drive Count area, review the following fields:

Name

Description

Physical Drive Count field

The number of FlexUtil cards detected in the server.

Step 5

In the General tab's Virtual Drive Count area, review the following fields:

Name

Description

Virtual Drive Count field

The number of virtual drives configured on the FlexUtil cards installed in the server.

Viewing Physical Drive Properties

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate FlexUtil controller.

Step 3

In the Physical Drive Info tab on the right pane, review the following fields:

Name

Description

Slot ID

The name of the PCIe slot in which the controller drive is located.

Disk Type

Whether the drive is a hard drive (HDD) or a solid state drive (SSD).

Status

The physical drive status. This can be one of the following:

  • Copyback—The drive is busy performing a copyback operation.

  • Failed—The drive was in use, but it has failed.

  • Foreign configuration—The drive contains a foreign configuration.

  • Global hot spare—The drive is designated as a global spare drive.

  • Dedicated hot spare—The drive is designated as a dedicated spare drive.

  • Offline—The drive is offline and cannot be accessed.

  • Online—The drive is in use as part of a drive group.

  • Predicted Failure—The drive is marked as due to fail soon by the controller.

  • Ready to remove—The drive is prepared for removal.

  • Rebuild—The drive is currently being rebuilt.

  • System—The drive is visible to the host and cannot be used for virtual drives.

  • Unconfigured bad—The drive has failed and is not in use.

  • Unconfigured good—The drive is ready to be assigned to a drive group or hot spare pool.

Capacity (GB)

The capacity of the drive in gigabytes.

Model

The drive vendor name.

Firmware

The firmware version running on the drive.

Step 4

Select a drive and review the following information in the new pane:

Table 16. Product Details

Name

Description

Power Cycle Count

Number of power cycles that the drive went through from the time it was manufactured.

Power on Hours

Total number of hours that the drive is in the 'Power On' mode.

Percentage Life Left

The number of write cycles remaining in a solid state drive (SSD). For instance, if an SSD is capable of 100 write cycles during its life time, and it has completed 15 writes, then the percentage of life left in the drive is 85%. Each percentage range is represented in a different color. For instance, green for 75% to 100% and red for 1 to 25%.

Wear Status in Days

The number of days an SSD has gone through with the write cycles.

SSD vendors provide a finite number of writes per day on the SSD, based on which, you can calculate the total number of years the SSD would continue to work.

Operating Temperature

The current temperature of the drive at which the selected SSD operates at the time of selection.

Maximum Operating Temperature

Allowable maximum temperature in which the drive can operate without errors.

Percentage Reserved Capacity Consumed

The total capacity (out of the percentage reserved for it) consumed by the drive.

Table 17. General Tab

Name

Description

Media Type

Whether the drive is a hard drive (HDD) or a solid state drive (SSD).

Interface Type

The drive interface type.

Sequence Number

The sequence number used by the controller to track drive changes.

Security Enabled

If this field displays Yes, full disk encryption is enabled on the physical drive.

Physical Block Size

Indicates the physical block size of the drive.

Slot Number

The slot number in which the physical drive resides.

Device ID

The device ID for the drive.

Product ID

The drive product ID. This field generally displays the drive model number.

UCS Product ID

Vendor

The vendor for the drive.

Drive Firmware

The active firmware version on the drive.

Drive Serial Number

The serial number for the drive.

Raw Size

The capacity of drive in megabytes, including the space used for formatting.

Non Coerced Size

The capacity in megabytes, including space lost to coercion.

Coerced Size

The capacity in megabytes after any coercion rounding has been performed.

Negotiated Link Speed

The speed of the link between the drive and the controller.
Table 18. Health Status

Name

Description

Locator LED toggle button

Allows you to turn on or off the drive LED.

Health

This field displays the health of the physical drive.

State

The drive status. This can be one of the following:

  • Cache degraded—A virtual drive with a Write Policy of Write Back was changed by the controller to Write Through because the BBU could not guarantee the coherency of the cache.

  • Copyback—The drive is busy performing a copyback operation.

  • Failed—The drive was in use, but it has failed.

  • Foreign configuration—The drive contains a foreign configuration.

  • Global hot spare—The drive is designated as a global spare drive.

  • Dedicated hot spare—The drive is designated as a dedicated spare drive.

  • Offline—The drive is offline and cannot be accessed.

  • Online—The drive is in use as part of a drive group.

  • Predicted Failure—The drive is marked as due to fail soon by the controller.

  • Ready to remove—The drive is prepared for removal.

  • Rebuild—The drive is currently being rebuilt.

  • System—The drive is visible to the host and cannot be used for virtual drives.

  • Unconfigured bad—The drive has failed and is not in use.

  • Unconfigured good—The drive is ready to be assigned to a drive group or hot spare pool.

Status

The physical drive status. This can be one of the following:

  • JBOD— The drive is in JBOD state.

  • Predicted Failure—The drive is marked as due to fail soon by the controller.

  • Unconfigured bad—The drive has failed and is not in use.

Copyback Operation Status

Copyback operation status. This can be one of the following:

  • Unknown— Percentage completed is not known.

  • In Progress— The rebuild process as seen in the Copyback Percent Complete field. When a hot spare is configured, and you remove a disk from the RAID group, and subsequently replace it, the rebuild occurs releasing the hot space.

  • Completed— Copyback operation is completed.

Copyback Percent Complete

Copyback operation completed, in percentage.

Power State field

The current power state. This can be one of the following:

  • active—The drive is running normally.

  • powersave—The drive has been spun down.

  • transitioning—The drive is spinning up.

Table 19. Error Count

Name

Description

Media Error Count

The number of media errors encountered since the drive was first installed or the host was rebooted.

Other Error Count

The number of non media errors encountered since the drive was first installed or the host was rebooted.

Predictive Failure Count

The number of times that the controller has predicted that the drive could fail.

Step 5

Click Close.

Viewing Virtual Drive Properties

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate FlexUtil controller.

Step 3

In the Virtual Drive Info tab on the right pane, review the following fields.

Table 20. Virtual Drive Info

Name

Description

ID

The number of the virtual drive. Click to see more details.

Name

The name of the virtual drive.

Status

The virtual drive state. This can be one of the following:

  • Cache degraded—The requested Write-cache policy for this drive is Write Back, but it is running in Write Through mode because the BBU is defective or is undergoing a learn cycle.

  • Degraded—One or more spans of the drive has no redundancy.

  • Off Line—The drive is not visible to the host.

  • Partially Degraded—The drive has lost some redundancy but still has partial redundancy. For example, if a 3-way RAID 1 mirrored drive lost one disk, it would still have 2-way redundancy.

  • Optimal—The drive has full redundancy.

Size (GB)

The capacity of the drive in megabytes.

RAID Level

The RAID level on the virtual drive. This can be one of the following:

  • Raid 0—Simple striping.

  • Raid 1—Simple mirroring.

  • Raid 5—Striping with parity.

  • Raid 6—Striping with two parity drives.

  • Raid 10—Spanned mirroring.

  • Raid 50—Striping with parity.

  • Raid 60—Spanned striping with two parity drives.

  • Raid 00—Spanned striping.

Boot Drive(s)

Whether the virtual drive has been designated as a boot drive.

Mapping an Image to a Virtual Drive

Before you begin

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

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate FlexUtil controller.

Step 3

Click the Virtual Drive Info tab on the right pane.

Step 4

Select the virtual drive and click Add Image.

Step 5

In the Add New Image dialog box, update the following fields:

Name Description

Volume field

The identity of the image mounted for mapping. This can be one of the following:

  • SCU

  • Diagnostics

  • HUU

  • Drivers

Mount Type drop-down list

The type of mapping. This can be one of the following:

  • NFS—Network File System.

  • CIFS—Common Internet File System.

  • WWW(HTTP/HTTPS)—HTTP-based or HTTPS-based system.

Remote Share field

The URL of the image to be mapped. The format depends on the selected Mount Type:

  • NFS—Use serverip:/share path.

  • CIFS—Use //serverip/share path.

  • WWW(HTTP/HTTPS)—Use http[s]://serverip/share.

Remote File field

The name and location of the .iso file in the remote share. Following are the example of remote share files:

  • NFS — /softwares/ucs-cxx-scu-3.1.9.iso

  • CIFS — /softwares/ucs-cxx-scu-3.1.9.iso

  • WWW(HTTP/HTTPS) — http[s]://softwares/ucs-cxx-scu-3.1.9.iso

Mount Options field

Industry-standard mount options entered in a comma separated list. The options vary depending on the selected Mount Type.

If you are using NFS, leave the field blank or enter one or more of the following:

  • ro

  • rw

  • nolock

  • noexec

  • soft

  • port=VALUE

  • timeo=VALUE

  • retry=VALUE

If you are using CIFS, leave the field blank or enter one or more of the following:

  • soft

  • nounix

  • noserverino

If you are using WWW(HTTP/HTTPS), leave the field blank or enter the following:

  • noauto

    Note

     

    Before mounting the image, Cisco IMC tries to verify reachability to the end server by pinging the server.

  • username=VALUE

  • password=VALUE

Updating an Image on the Virtual Drive

Before you begin

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

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate FlexUtil controller.

Step 3

Click the Virtual Drive Info tab on the right pane.

Step 4

Click the Virtual Drives tab.

Step 5

In the Virtual Drives area, select the virtual drive for which you want to update an image and click Update Image.

Step 6

Optional: If you want to cancel an ongoing update operation, click Cancel Update.

Unmapping an Image From a Virtual Drive

Before you begin

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

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate FlexUtil controller.

Step 3

Click the Virtual Drive Info tab on the right pane.

Step 4

Select the virtual drive for which you want to delete the image and click Unmap Image.

Erasing a Virtual Drive

Before you begin

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

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate FlexUtil controller.

Step 3

Click the Virtual Drive Info tab on the right pane.

Step 4

In the Virtual Drive Info area, select the virtual drive you want to erase, and click Erase Virtual Drive.

Cisco Boot Optimized M.2 Raid Controller

Viewing Cisco Boot Optimized M.2 Raid Controller Details

Before you begin

The server must be powered on.

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate M.2 Raid controller controller.

Step 3

In the Controller Info tab > General tab on the right pane, review the following information:

Name

Description

Product Name

The name of the MegaRAID controller.

Product ID

Cisco part number of the RAID controller.

Composite Health

The combined health of the controller, the attached drives, and the battery backup unit. This can be one of the following:

  • Good

  • Moderate Fault

  • Severe Fault

  • N/A

Controller Status

The current status of the controller. This can be one of the following:

  • Optimal — The controller is functioning properly.

  • Failed — The controller is not functioning.

  • Unresponsive — The controller is down.

Security

Displays the controller lock key depending on its current state.

Note

 

  • This option is available only on some C-Series servers.

  • Disabling the drive security makes the data on all secure drives unusable.

Serial Number field

The serial number of the MegaRAID controller.

RAID Chip Temperature field

Temperature of the controller in degree centigrade.

Firmware Package Build field

The active firmware package version number.

For the firmware component version numbers, see the Running Firmware Images area.

Consistency Check Rate field

The rate at which the controller scans the virtual drives looking for redundant data inconsistencies and fixing them.

This rate is shown as a percentage of the total bandwidth available.

PCI Slot

The name of the PCIe slot in which the controller is located.

Vendor ID

The PCI vendor ID, in hexadecimal.

SubVendor ID

The PCI subvendor ID, in hexadecimal.

Device ID

The PCI device ID, in hexadecimal.

Sub Device ID

The PCI subdevice ID, in hexadecimal.

Manufactured Date

The date the MegaRAID card was manufactured, in the format yyy-mm-dd.

Revision

The board revision number, if any.

Boot Drive(s)

The number of the boot drive.

Interface Type

Whether the drive is SAS or SATA

Step 4

In the Controller Info tab > Settings tab on the right pane, review the following information:

Table 21. Settings Area

Name

Description

Physical Drive Status Auto Config Mode

The physical drive status auto config mode that you select for the controller. This can be one of the following:

  • Unconfigured Good - The default option. Select this option if you are using the server for RAID volume and mixed JBOD.

  • RAID-0 Write Back - Select this option if you are using the server for per drive R0 WB.

  • JBOD - Select this option if you are using the server for JBOD only.

Rebuild Rate

The rate at which the controller rebuilds degraded RAID volumes.

This rate is shown as a percentage of the total bandwidth available.

Patrol Read Rate

The rate at which the controller performs a background read of the physical drives looking for inconsistent data.

This rate is shown as a percentage of the total bandwidth available.

Consistency Check Rate

The rate at which the controller scans the virtual drives looking for redundant data inconsistencies and fixing them.

This rate is shown as a percentage of the total bandwidth available.

ECC Bucket Leak Rate

The error correcting code (ECC) single-bit error bucket leak rate, in minutes.

With ECC, the controller increments an error counter when it encounters a single bit error while reading from a physical drive. The controller decrements the error counter each time the number of minutes defined in this field passes.

If the error counter reaches a system-defined maximum, the controller sends an event message to the system.

JBOD

If this field displays true, JBOD is enabled.

Maintain PD Fail History

If this field displays true, the controller remembers which physical drives were determined to be bad across server reboots.

Battery Warning

If this field displays true, missing battery warnings are disabled.

Table 22. HW Config Area

Name

Description

Controller SAS Address

A MegaRAID controller can have up to 16 serial-attached SCSI (SAS) addresses. This field displays the first 8 SAS addresses, if they are in use.

BBU Present

If this field displays true, the battery backup unit is present.

Memory Present

If this field displays true, memory is present.

Flash Present

If this field displays true, flash memory is present.

Table 23. Capabilities Area

Name

Description

RAID Levels Supported

The RAID levels supported by the controller. This can be one or more of the following:

  • Raid 0—Simple striping.

  • Raid 1—Simple mirroring.

  • Raid 5—Striping with parity.

  • Raid 1E—Integrated offset strip mirroring

  • Raid 6—Striping with two parity drives.

  • Raid 10—Spanned mirroring.

  • Raid 50—Spanned striping with parity.

  • Raid 60—Spanned striping with two parity drives.

  • Raid srl-03—Spanned secondary RAID level

  • Raid 00—Spanned striping.

  • Raid 1e-rlq0—Integrated adjacent strip mirroring with no span.

  • Raid 1e0-rlq0—Integrated adjacent strip mirroring with span.
Table 24. Error Counters Area

Name

Description

Memory Correctable Errors

The number of correctable errors in the controller memory.

Viewing Physical Drive Info for Cisco Boot Optimized M.2 Raid Controller

Before you begin

The server must be powered on.

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate M.2 raid controller.

Step 3

Click Physical Drive Info tab on the right pane and review the following information:

Name

Description

Slot ID

The name of the PCIe slot in which the controller drive is located.

Disk Type

Whether the drive is a hard drive (HDD) or a solid state drive (SSD).

Status

The physical drive status. This can be one of the following:

  • Copyback—The drive is busy performing a copyback operation.

  • Failed—The drive was in use, but it has failed.

  • Foreign configuration—The drive contains a foreign configuration.

  • Global hot spare—The drive is designated as a global spare drive.

  • Dedicated hot spare—The drive is designated as a dedicated spare drive.

  • Offline—The drive is offline and cannot be accessed.

  • Online—The drive is in use as part of a drive group.

  • Predicted Failure—The drive is marked as due to fail soon by the controller.

  • Ready to remove—The drive is prepared for removal.

  • Rebuild—The drive is currently being rebuilt.

  • System—The drive is visible to the host and cannot be used for virtual drives.

  • Unconfigured bad—The drive has failed and is not in use.

  • Unconfigured good—The drive is ready to be assigned to a drive group or hot spare pool.

Capacity (GB)

The capacity of the drive in gigabytes.

Model

The drive vendor name.

Firmware

The firmware version running on the drive.

Step 4

Select a drive and review the following information that is displayed on a new pane:

Table 25. General Tab

Name

Description

Media Type

Whether the drive is a hard drive (HDD) or a solid state drive (SSD).

Interface Type

The drive interface type.

Sequence Number

The sequence number used by the controller to track drive changes.

Security Enabled

If this field displays Yes, full disk encryption is enabled on the physical drive.

Physical Block Size

Indicates the physical block size of the drive.

Slot Number

The slot number in which the physical drive resides.

Device ID

The device ID for the drive.

Product ID

The drive product ID. This field generally displays the drive model number.

UCS Product ID

Vendor

The vendor for the drive.

Drive Firmware

The active firmware version on the drive.

Drive Serial Number

The serial number for the drive.

Raw Size

The capacity of drive in megabytes, including the space used for formatting.

Non Coerced Size

The capacity in megabytes, including space lost to coercion.

Coerced Size

The capacity in megabytes after any coercion rounding has been performed.

Negotiated Link Speed

The speed of the link between the drive and the controller.
Table 26. Health Status

Name

Description

Locator LED toggle button

Allows you to turn on or off the drive LED.

Health

This field displays the health of the physical drive.

State

The drive status. This can be one of the following:

  • Cache degraded—A virtual drive with a Write Policy of Write Back was changed by the controller to Write Through because the BBU could not guarantee the coherency of the cache.

  • Copyback—The drive is busy performing a copyback operation.

  • Failed—The drive was in use, but it has failed.

  • Foreign configuration—The drive contains a foreign configuration.

  • Global hot spare—The drive is designated as a global spare drive.

  • Dedicated hot spare—The drive is designated as a dedicated spare drive.

  • Offline—The drive is offline and cannot be accessed.

  • Online—The drive is in use as part of a drive group.

  • Predicted Failure—The drive is marked as due to fail soon by the controller.

  • Ready to remove—The drive is prepared for removal.

  • Rebuild—The drive is currently being rebuilt.

  • System—The drive is visible to the host and cannot be used for virtual drives.

  • Unconfigured bad—The drive has failed and is not in use.

  • Unconfigured good—The drive is ready to be assigned to a drive group or hot spare pool.

Status

The physical drive status. This can be one of the following:

  • JBOD— The drive is in JBOD state.

  • Predicted Failure—The drive is marked as due to fail soon by the controller.

  • Unconfigured bad—The drive has failed and is not in use.

Copyback Operation Status

Copyback operation status. This can be one of the following:

  • Unknown— Percentage completed is not known.

  • In Progress— The rebuild process as seen in the Copyback Percent Complete field. When a hot spare is configured, and you remove a disk from the RAID group, and subsequently replace it, the rebuild occurs releasing the hot space.

  • Completed— Copyback operation is completed.

Copyback Percent Complete

Copyback operation completed, in percentage.

Power State field

The current power state. This can be one of the following:

  • active—The drive is running normally.

  • powersave—The drive has been spun down.

  • transitioning—The drive is spinning up.

Table 27. Error Count

Name

Description

Media Error Count

The number of media errors encountered since the drive was first installed or the host was rebooted.

Other Error Count

The number of non media errors encountered since the drive was first installed or the host was rebooted.

Predictive Failure Count

The number of times that the controller has predicted that the drive could fail.

Table 28. Product Details

Name

Description

Power Cycle Count

Number of power cycles that the drive went through from the time it was manufactured.

Power on Hours

Total number of hours that the drive is in the 'Power On' mode.

Percentage Life Left

The number of write cycles remaining in a solid state drive (SSD). For instance, if an SSD is capable of 100 write cycles during its life time, and it has completed 15 writes, then the percentage of life left in the drive is 85%. Each percentage range is represented in a different color. For instance, green for 75% to 100% and red for 1 to 25%.

Wear Status in Days

The number of days an SSD has gone through with the write cycles.

SSD vendors provide a finite number of writes per day on the SSD, based on which, you can calculate the total number of years the SSD would continue to work.

Operating Temperature

The current temperature of the drive at which the selected SSD operates at the time of selection.

Maximum Operating Temperature

Allowable maximum temperature in which the drive can operate without errors.

Percentage Reserved Capacity Consumed

The total capacity (out of the percentage reserved for it) consumed by the drive.

Step 5

Click Close.

Viewing the Virtual Drive Info for Cisco Boot Optimized M.2 Raid Controller

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

From Storage > Controllers, click the appropriate M.2 Raid controller.

Step 3

Select the Virtual Drive Info tab and review the following information:

Table 29. Virtual Drive Info

Name

Description

ID

The number of the virtual drive. Click to see more details.

Name

The name of the virtual drive.

Status

The virtual drive state. This can be one of the following:

  • Cache degraded—The requested Write-cache policy for this drive is Write Back, but it is running in Write Through mode because the BBU is defective or is undergoing a learn cycle.

  • Degraded—One or more spans of the drive has no redundancy.

  • Off Line—The drive is not visible to the host.

  • Partially Degraded—The drive has lost some redundancy but still has partial redundancy. For example, if a 3-way RAID 1 mirrored drive lost one disk, it would still have 2-way redundancy.

  • Optimal—The drive has full redundancy.

Size (GB)

The capacity of the drive in megabytes.

RAID Level

The RAID level on the virtual drive. This can be one of the following:

  • Raid 0—Simple striping.

  • Raid 1—Simple mirroring.

  • Raid 5—Striping with parity.

  • Raid 6—Striping with two parity drives.

  • Raid 10—Spanned mirroring.

  • Raid 50—Striping with parity.

  • Raid 60—Spanned striping with two parity drives.

  • Raid 00—Spanned striping.

Boot Drive(s)

Whether the virtual drive has been designated as a boot drive.

Step 4

Select a virtual drive and review the following information:

Table 30. RAID Details

Name

Description

Name

The name of the virtual drive.

Strip Size

The size of each strip, in KB.

Drives Per Span

The number of drives included in each span.

Span Depth

The number of spans that comprise the virtual drive.

Dedicated Hot Spare Drives

Access Policy field

The method the host operating system can use to access the virtual drive. This can be one of the following:

  • Blocked—The host cannot access the drive.

  • Read-Write—The host has full access to the drive.

  • Read-Only—The host can only read data from the drive.

Cache Policy field

The cache policy. This can be one of the following:

  • Allow—Reads and writes are cached in the controller.

  • Allow Read—Only reads are cached in the controller.

  • Allow Write—Only writes are cached in the controller.

  • Direct—Neither reads or writes are cached in the controller.

Read Ahead Policy field

How the controller uses the read-ahead feature. This can be one of the following:

  • Adaptive—Read-ahead is enabled and used when the controller thinks it will improve performance.

  • Always—Read-ahead is enabled and always used.

  • None—Read-ahead is disabled.

Security Capable

If this field displays Yes, it indicates that the physical drive is security-capable.

Consistency Check Operation Status

Requested Write Cache Policy

How the controller handles caching. This can be one of the following:

  • Write Through—Data written is stored in the cache and also written through to the physical drives. The transaction is not marked complete until data is written to the physical drives.

  • Write Back—Data written is stored in the cache and will be written to the physical drives when bandwidth is available. This policy has higher write performance than the Write Through mode, but it falls back to the Write Through mode when the BBU is defective or is in a learn cycle.

  • Write Back Even If Bad BBU—Caching remains in Write Back mode even if the BBU is bad.

    Data can be lost in this mode if there is a power failure.

Current Write Cache Policy

The currently running cache policy. This can be one of the following:

  • Write Through—Data written is stored in the cache and also written through to the physical drives. The transaction is not marked complete until data is written to the physical drives.

  • Write Back—Data written is stored in the cache and will be written to the physical drives when bandwidth is available. This policy has higher write performance than the Write Through mode, but it falls back to the Write Through mode when the BBU is defective or is in a learn cycle.

  • Write Back Even If Bad BBU—Caching remains in Write Back mode even if the BBU is bad.

    Data can be lost in this mode if there is a power failure.

Disk Cache Policy

How the controller handles physical disk caching. This can be one of the following:

  • Disable—Caching is disabled on the physical drives.

  • Enable—Caching is enabled on the physical drives.

  • Unchanged—The controller uses the caching policy specified on the physical drive.

Note

 

If several virtual drives share a drive group, they must all use the same disk cache policy. Otherwise the caching policy may be randomly assigned to the physical drives.

Boot Drive

If this field displays true, then the virtual drive is designated as a boot drive.

Security Enable

If this field displays Yes, full disk encryption is enabled on the physical drive.

Step 5

Click Close.

Cisco FlexMMC

Viewing Cisco FlexMMC Details

Procedure

Step 1

From the Apps drop-down list, select Storage.

Step 2

In the Storage page, click Cisco FlexMMC.

Step 3

In the Storage for IMC Images area, view the following:

Table 31. Storage for IMC Images Area

Name

Description

Storage for IMC Images pie chart

Helps you analyze the total, available, and used spaces for the Cisco IMC images.

File Name column

Cisco IMC image file names.

File Size column

Cisco IMC image file size.

File Type column

Cisco IMC image file type.

Status column

Status of the Cisco IMC image file.

Step 4

In the Storage for User Files Area area, view the following:

Table 32. Storage for User Files Area

Name

Description

Storage for User Files pie chart

Helps you analyze the total, available, and used spaces for the user files.

File Name column

User file names.

File Size column

User file size.

File Type column

User file type.

Status column

Status of the user file.

Uploading New Image File

Before you begin

Ensure that there are no file upload in progress. You can upload only one image file at any time. To upload a new file, you should first un-map and delete the existing file.

SUMMARY STEPS

  1. From the Apps drop-down list, select Storage.
  2. In the Storage page, click Cisco FlexMMC.
  3. In the Storage for IMC Images area, click Upload File.
  4. In the Upload File to IMC Images partition dialog box, complete the following:
  5. Click Save.

DETAILED STEPS

Step 1

From the Apps drop-down list, select Storage.

Step 2

In the Storage page, click Cisco FlexMMC.

Step 3

In the Storage for IMC Images area, click Upload File.

The Upload File to IMC Images partition dialog box is displayed.

Step 4

In the Upload File to IMC Images partition dialog box, complete the following:

Name Description

File Location field

The URL of the image to be mapped. The format depends on the selected Mount Type:

  • NFS—Use serverip:/share.

  • CIFS—Use //serverip/share.

  • WWW(HTTP/HTTPS)—Use http[s]://serverip/share.

Mount Options field

Industry-standard mount options entered in a comma separated list. The options vary depending on the selected Mount Type.

If you are using NFS, leave the field blank or enter one or more of the following:

  • ro

  • rw

    Note

     

    The folder, which is shared, should have write permissions to use read-write option. Read-write option is available only for .img files.

  • nolock

  • noexec

  • soft

  • port=VALUE

  • timeo=VALUE

  • retry=VALUE

  • rsize=VALUE

  • wsize=VALUE

  • vers=VALUE

If you are using CIFS, leave the field blank or enter one or more of the following:

  • ro

  • rw

    Note

     

    The folder, which is shared, should have write permissions to use read-write option. Read-write option is available only for .img files.

  • soft

  • nounix

  • noserverino

  • guest

  • username=VALUE—ignored if guest is entered.

  • password=VALUE—ignored if guest is entered.

  • sec=VALUE

    The protocol to use for authentication when communicating with the remote server. Depending on the configuration of CIFS share, VALUE could be one of the following:

    • None—No authentication is used

    • Ntlm—NT LAN Manager (NTLM) security protocol. Use this option only with Windows 2008 R2 and Windows 2012 R2.

    • Ntlmi—NTLMi security protocol. Use this option only when you enable Digital Signing in the CIFS Windows server.

    • Ntlmssp—NT LAN Manager Security Support Provider (NTLMSSP) protocol. Use this option only with Windows 2008 R2 and Windows 2012 R2.

    • Ntlmsspi—NTLMSSPi protocol. Use this option only when you enable Digital Signing in the CIFS Windows server.

    • Ntlmv2—NTLMv2 security protocol. Use this option only with Samba Linux.

    • Ntlmv2i—NTLMv2i security protocol. Use this option only with Samba Linux.

  • vers=VALUE

    Note

     

    The format of the VALUE should be x.x

If you are using WWW(HTTP/HTTPS), leave the field blank or enter the following:

  • noauto

    Note

     

    Before mounting the virtual media, Cisco IMC tries to verify reachability to the end server by pinging the server.

  • username=VALUE

  • password=VALUE

Username field

Note

 

This field is not available for NFS mount.

The username for the specified Mount Type, if required.

Password field

Note

 

This field is not available for NFS mount.

The password for the selected username, if required.

Add button

Allows you to add the file in the system.

Step 5

Click Save.

You can view the file upload status under Files Copied area.

Note

 

If you wish to cancel the upload process before it is completed, select the file and click Cancel Upload.

Deleting an Image File

Before you begin

  • Ensure that there are no file uploads in progress. You cannot delete a file for which the upload is in progress.

  • Ensure that there are no files mapped. You cannot delete a file which is already mapped. You should first un-map the file before deleting the file.

SUMMARY STEPS

  1. In the Navigation pane, click the Storage menu.
  2. From the Apps drop-down list, select Storage.
  3. In the Storage page, click Cisco FlexMMC.
  4. In the Storage for IMC Images area > Files Copied area, select an image file.
  5. Click Delete File.

DETAILED STEPS

Step 1

In the Navigation pane, click the Storage menu.

Step 2

From the Apps drop-down list, select Storage.

Step 3

In the Storage page, click Cisco FlexMMC.

Step 4

In the Storage for IMC Images area > Files Copied area, select an image file.

Step 5

Click Delete File.

Mapping or Un-mapping an Image

SUMMARY STEPS

  1. From the Apps drop-down list, select Storage.
  2. In the Storage page, click Cisco FlexMMC.
  3. In the Storage for IMC Images area > Files Copied area, select an image file.
  4. Click Map Image or UnMap Image.

DETAILED STEPS

Step 1

From the Apps drop-down list, select Storage.

Step 2

In the Storage page, click Cisco FlexMMC.

Step 3

In the Storage for IMC Images area > Files Copied area, select an image file.

Step 4

Click Map Image or UnMap Image.

Resetting FlexMMC to Default Settings

Perform this procedure to reset FlexMMC to default Cisco IMC settings.


Note

Performing this procedure deletes all the uploaded images.

Before you begin

  • Ensure that there are no file uploads in progress. You cannot reset FlexMMC to default settings while a file upload is in progress.

  • Ensure that there are no files mapped. You cannot reset FlexMMC if a file is already mapped. You should first un-map the file before resetting FlexMMC.

Procedure

  Command or Action Purpose

Step 1

From the Apps drop-down list, select Storage.

Step 2

In the Storage page, click Cisco FlexMMC.

Step 3

In the Actions drop-down list on the right pane, select Reset to Defaults.

Step 4

Click Yes to confirm.