Cisco UCS: Configuring and Managing Intel® Optane™ Data Center Persistent Memory Modules

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco UCS: Configuring and Managing Intel® Optane™ Data Center Persistent Memory Modules

Chapter Title

Configuring Persistent Memory Using Cisco UCS Manager GUI

Results

Updated:
June 24, 2021

Chapter: Configuring Persistent Memory Using Cisco UCS Manager GUI

Configuring Persistent Memory Using Cisco UCS Manager GUI

Creating a Persistent Memory Policy

Procedure

Step 1

In the Navigation pane, click Servers.

Step 2

Expand Servers > Policies.

Step 3

Expand the node for the organization where you want to create the policy.

If the system does not include multi tenancy, expand the root node.

Step 4

Right-click Persistent Memory Policy and select Create Persistent Memory Policy.

Step 5

In the Properties area of the Create Persistent Memory Policy dialog box, enter the following information:

Name

Description

Name field

The name of the persistent memory policy. This is a mandatory field.

Description field

A short description of the policy.

Step 6

To create a goal, click the Add button in the Goals area of the Create Persistent Memory Policy dialog box and complete the fields.

Creating a Goal has detailed information.

Step 7

Click OK.

Step 8

To create a namespace, click the Add button in the Configure Namespace area of the Create Persistent Memory Policy dialog box and complete the fields.

Creating a Namespace has detailed information.

Step 9

Click OK.

Including a Persistent Memory Policy in a Service Profile

Before you can use a persistent memory policy to manage persistent memory in Cisco UCS Manager, you must include the persistent memory policy in a service profile. After a persistent memory policy is included in a service profile, you can associate the service profile with a Cisco UCS server.

If you include a persistent memory policy in a service profile associated to a server, the persistent memory configuration on the server is UCS-managed. In the UCS-managed mode, you can use Cisco UCS Manager and host tools to configure and manage persistent memory modules.

If a persistent memory policy is not included in the service profile associated to a server, the persistent memory configuration on the server is host-managed. In the host-managed mode, you can use the host tools to configure and manage persistent memory modules.

The following procedure describes how to include a persistent memory policy in a service profile.

Before you begin

Create the persistent memory policy that you want to include in a service profile.

Procedure

Step 1

In the Navigation pane, click Servers.

Step 2

Expand Server > Service Profiles

Step 3

Select the service profile in which you want to include the persistent memory policy.

Step 4

In the Work pane, click the Policies tab.

Step 5

In the Policies area, expand Persistent Memory Policy.

Step 6

From the Persistent Memory Policy drop-down list, select the persistent memory policy that you want to include in this service profile.

Step 7

Click Save Changes.

The persistent memory policy is applied on the server to which the service profile is associated.

Removing a Persistent Memory Policy from a Service Profile

Removing a persistent memory policy from a service profile does not change any region or namespace configuration. It changes persistent memory from UCS-managed to host-managed. The following procedure describes how to remove a persistent memory policy from a service profile.

After you remove the persistent memory policy from the service profile that is associated to a server, the server is considered host-managed with respect to persistent memory configuration.

Procedure

Step 1

In the Navigation pane, click Servers.

Step 2

Expand Server > Service Profiles

Step 3

Select the service profile from which you want to remove the persistent memory policy.

Step 4

In the Work pane, click the Policies tab.

Step 5

In the Policies area, expand Persistent Memory Policy.

Step 6

From the Persistent Memory Policy drop-down list, select <not set>.

Step 7

Click Save Changes.

The persistent memory policy is removed from the service profile and its associated server.

Creating a Goal

Procedure

Step 1

In the Navigation pane, click Servers.

Step 2

Expand Servers > Policies.

Step 3

Expand the node for the organization where you want to create the goal.

Step 4

Select the persistent memory policy in which you want to create the goal.

Step 5

In the Goals area of the General tab, click the Add button.

Step 6

In the Create Goal dialog box, enter the following information:

Name

Description

Socket ID radio button

The CPU sockets on which the configured goal is applied.

The default option is All-Sockets.

Memory Mode (%) field

The percentage of memory on the persistent memory module that is configured as volatile memory.

  • When Memory Mode is set to 100%, it can be used completely as volatile memory.

  • When Memory Mode is set to 0%, it becomes App Direct Mode and can be used completely as persistent memory.

  • When Memory Mode is set to x%, x% is used as memory and the remaining is used as persistent memory. This is called Mixed Mode.

Note

 

  • The default memory mode percentage for:

    • UCS M5 B-Series and C-Series servers is 100%.

    • UCS M5 S-Series servers is 0%.

  • For UCS M6 B-Series and C-Series servers:

    • The Mixed Mode is not supported. For 8+1 POR, the App Direct Non Interleaved Mode is the only supported configuration.

    • The default memory mode percentage is 0%.

  • For UCS M5 and M6 servers, the Near Memory (NM) : Far Memory ratio (FM) (DRAM + PMEM) is supported between 1:4 - 1:16 in 100% memory mode.

Persistent Memory Type radio button

The type of persistent memory. This can be one of the following:

  • App Direct—Configures one region for all the persistent memory modules connected to a socket.

  • App Direct Non Interleaved—Configures one region for each persistent memory module.

Step 7

Click OK.

Creating a Namespace

Procedure

Step 1

In the Navigation pane, click Servers.

Step 2

Expand Servers > Policies.

Step 3

Expand the node for the organization where you want to create the namespace.

Step 4

Select the persistent memory policy in which you want to create the namespace.

Step 5

In the Configure Namespace area of the General tab, click the Add button.

Step 6

In the Create Namespace dialog box, enter the following information:

Name

Description

Name field

The name of the namespace.

The namespace name has the following constraints:

  • Must be between 1 and 63 characters in length.

  • The first character must be a letter (A-Z or a-z), a number(0-9), or a special character(#, -, or _ )

  • The remaining characters can be a combination of letters (A-Z or a-z), numbers (0-9), and special characters (#, -, _, space)

Socket ID drop-down list

The CPU socket ID for the region to which this namespace belongs. This can be:

  • Socket 1

  • Socket 2

  • Socket 3

  • Socket 4

Note

 

For UCS M6 B-Series and C-Series servers, only Socket 1and Socket 2 are supported.

Socket Local DIMM Number drop-down list

The local DIMM number for the region to which this namespace belongs. This can be:

  • The only option avilable for App Direct persistent memory type—Not Applicable

  • The options available for the App Direct Non Interleaved persistent memory type include:

    • Socket Local DIMM No 2

    • Socket Local DIMM No 3

    • Socket Local DIMM No 4

    • Socket Local DIMM No 6

    • Socket Local DIMM No 7

    • Socket Local DIMM No 8

    • Socket Local DIMM No 10

    • Socket Local DIMM No 11

    • Socket Local DIMM No 12

    • Socket Local DIMM No 14

    • Socket Local DIMM No 15

    • Socket Local DIMM No 16

Note

 

The Socket Local DIMM No 3, 7, 11, 14, 15, and 16 are applicable only for UCS M6 B-Series and C-series servers.

Mode radio button

The mode in which the namespace is created. This can be:

  • Raw

  • Block

Capacity field

The memory capacity of the namespace in GiBs.

Step 7

Click OK.

Creating Local Security Configuration

Procedure

Step 1

In the Navigation pane, click Servers.

Step 2

Expand Servers > Policies.

Step 3

Expand the node for the organization where you want to configure the persistent memory security.

Step 4

Select the persistent memory policy for which you want to configure the security.

Step 5

In the Actions area of the Security tab, click Create Local Security.

Step 6

In the Create Local Security dialog box, enter the following information:

Name

Description

Secure Passphrase field

The secure passphrase to be set for the persistent memory policy.

The secure passphrase has the following constraints:

  • Must be between 8 and 32 characters in length.

  • These characters can be a combination of letters (A-Z or a-z), numbers (0-9), and special characters (!, @, #, $, %, ^, &, *, -, _, +, =).

Deployed Secure Passphrase field

Currently deployed secure passphrase for the persistent memory policy.

The Deployed Secure Passphrase is required when the server that you are configuring has a secure passphrase from a previous deployment. This is required only for secure passphrase modification.

Step 7

Click OK.

Modifying a Persistent Memory Policy

Procedure

Step 1

In the Navigation pane, click Servers.

Step 2

Expand Servers > Policies.

Step 3

Expand Persistent Memory Policy and select the persistent memory policy that you want to modify.

Step 4

In the Properties area of the General tab, modify the following:

  1. Description field—Enter a short description of the policy.

  2. Force Configuration checkbox—Check this checkbox to force the configuration on all associated servers. Clear this checkbox to return this to the default state.

Step 5

Click Save Changes.

Modifying a Goal

Modifying a goal will result in the loss of data currently stored in the persistent memory.

Because goal modification is a destructive operation, you must check the Force Configuration checkbox before modifying the goal.

Before modifying the Persistent Memory Type, delete the existing namespaces. This is because, in the App Direct persistent memory type you do not specify a DIMM number for each namespace. In the App Direct Non Interleaved persistent memory type, each namespace has a DIMM number specified.

Procedure

Step 1

In the Navigation pane, click Servers.

Step 2

Expand Servers > Policies.

Step 3

Expand Persistent Memory Policy and select the persistent memory policy within which you want to modify a goal.

Step 4

In the Properties area of the General tab, check the Force Configuration checkbox.

Step 5

In the Goals area of the General tab, select the goal to be modified and click Modify.

Step 6

In the dialog box that appears, modify the following:

  1. In the Memory Mode (%) field, enter the percentage of memory on the persistent memory module to be configured as volatile memory.

    Note

     

    • The default memory mode percentage for UCS M5 and M6 B-Series and C-Series servers is 100%.

    • The default memory mode percentage for UCS M5 S-Series servers is 0%.

  2. Select the Persistent Memory Type.

    • App Direct—Configures one region for all the persistent memory modules connected to a socket.

    • App Direct Non Interleaved—Configures one region for each persistent memory module.

    To modify the Persistent Memory Type, you must first delete the existing namespaces.

Step 7

Click OK.

Step 8

In the General tab, click Save Changes.

Modifying a Namespace

You can modify a namespace only if the persistent memory policy that contains the namespace is not referred to by a server. Modifying a namespace is not an allowed operation if the persistent memory policy that contains the namespace is referred to by a server.

The following steps are applicable only when the persistent memory policy that contains the namespace is not referred to by a server.

Procedure

Step 1

In the Navigation pane, click Servers.

Step 2

Expand Servers > Policies.

Step 3

Expand Persistent Memory Policy and select the persistent memory policy within which you want to modify a namespace.

Step 4

In the Namespaces area of the General tab, select the namespace to be modified and click Modify.

Step 5

In the dialog box that appears, modify the following:

  1. Select the persistent memory Mode for the namespace.

    • Raw

    • Block

  2. In the Capacity field, modify the capacity of the namespace.

Step 6

Click OK.

Step 7

In the General tab, click Save Changes.

Modifying Local Security Configuration

Procedure

Step 1

In the Navigation pane, click Servers.

Step 2

Expand Servers > Policies.

Step 3

Expand the node for the organization where you want to modify the persistent memory security.

Step 4

Select the persistent memory policy for which you want to modify the security.

Step 5

In the Local Security area of the Security tab, enter the following information:

Name

Description

Secure Passphrase field

The new secure passphrase to be set for the persistent memory policy.

Deployed Secure Passphrase field

The currently deployed secure passphrase for the persistent memory policy.

The secure passphrase entered in this field must match the currently deployed secure passphrase.

Step 6

Click Save Changes.

Deleting a Persistent Memory Policy

You cannot delete a persistent memory policy when the policy is referred to by a server. To delete a persistent memory policy when it is not referred to by a server, follow these steps:

Procedure

Step 1

In the Navigation pane, click Servers.

Step 2

Expand Servers > Policies.

Step 3

Click Persistent Memory Policy and in the Work pane, select the persistent memory policy that you want to delete.

Step 4

Click Delete.

Step 5

Click Yes to confirm deletion.

Deleting a Goal

For UCS M5 and M6 B-Series and C-Series servers, deleting a goal deletes all related regions and namespaces on the associated servers, and disables security. For UCS M5 S-Series servers, deleting a goal deletes all namespaces on the associated servers, and disables security. Goal deletion also returns the persistent memory module to its default state. The default state of a persistent memory module is:

  • UCS M5 and M6 B-Series and C-Series servers—100% Memory Mode and App Direct persistent memory type

  • UCS M5 S-Series servers—0% Memory Mode and App Direct Non Interleaved persistent memory type

Because goal deletion is a destructive operation, you must check the Force Configuration checkbox before deleting the goal.

Procedure

Step 1

In the Navigation pane, click Servers.

Step 2

Expand Servers > Policies.

Step 3

Expand Persistent Memory Policy and select the persistent memory policy within which you want to delete a goal.

Step 4

In the Properties area of the General tab, check the Force Configuration checkbox.

Step 5

In the Goals area of the General tab, select the goal to be deleted and click Delete.

Step 6

Click OK.

Step 7

In the General tab, click Save Changes.

Deleting a Namespace

Deleting a namespace will result in the loss of data currently stored in the namespace.

Because namespace deletion is a destructive operation, you must check the Force Configuration checkbox before deleting the namespace.

Procedure

Step 1

In the Navigation pane, click Servers.

Step 2

Expand Servers > Policies.

Step 3

Expand Persistent Memory Policy and select the persistent memory policy within which you want to delete a namespace.

Step 4

In the Properties area of the General tab, check the Force Configuration checkbox.

Step 5

In the Namespaces area of the General tab, select the namespace to be deleted and click Delete.

Step 6

Click OK.

Step 7

In the General tab, click Save Changes.

Deleting Local Security Configuration

Deleting the security configuration will disable security.

Procedure

Step 1

In the Navigation pane, click Servers.

Step 2

Expand Servers > Policies.

Step 3

Expand the node for the organization where you want to delete the persistent memory security.

Step 4

Select the persistent memory policy for which you want to delete local security.

Step 5

In the Actions area of the Security tab, click Delete Local Security.

Step 6

In the Delete confirmation dialog box that appears, click Yes.

Physical Configuration and Inventory for Persistent Memory

You can view the physical inventory and configuration of all the persistent memory modules on a B-Series, C-Series, or S-Series server. The following parameters are detailed:

  • DIMMs—Properties of persistent memory modules.

    Persistent memory modules on the same server are locked by using a single secure passphrase. If locked persistent memory modules are brought over from a different server, they need to be unlocked before they can be managed from the new server.

  • Configuration—Overall server-level persistent memory configuration.

  • Region—Properties of all the regions on the server.

    A region is a grouping of one or more persistent memory modules that can be divided up into one or more namespaces. A region is created based on the persistent memory type selected during goal creation.

    The App Direct persistent memory type configures one region for all the memory modules connected to a socket. The App Direct Non Interleaved persistent memory type configures one region for each memory module.

  • Namespace—Properties of all the logical namespaces available on the server.

    These namespaces are seen by the host OS as block devices or raw devices.

Secure Erase

You can perform secure erase on a specific persistent memory module or all the persistent memory modules on a server. This operation deletes the region data and namespaces.

For the secure erase operation, you must provide a secure passphrase when security is enabled. When security is disabled, a secure passphrase in not required for the secure erase operation.

Viewing the Persistent Memory Modules on a Server

You can view the inventory of all the persistent memory modules on a B-Series, C-Series, or S-Series server.

Procedure

Step 1

In the Navigation pane, click Equipment.

Step 2

Expand to a server using one of the following paths:

  • For a blade server, expand Equipment > Chassis > Chassis-Number > Servers
  • For a rack-mount server, expand Equipment > Rack Mounts > Servers

Step 3

Select the server for which you want to view the persistent memory module inventory.

Step 4

In the Work pane, click the Inventory tab and then the Persistent Memory subtab.

Step 5

Click the DIMMS subtab. The following information appears:

Name

Description
Selectcolumn

Checkbox that allows selection of one or more persistent memory modules. Use this for Secure Erase and Unlock Foreign DIMMs actions only.

Namecolumn

A navigation tree that allows you to view a particular component and its subcomponents. You can right-click a component to view any actions available for that component.

Clock (MHZ)column

The speed at which the memory bus is running in Megahertz.

Location column

The location in which the persistent memory module is installed.

Socket ID drop-down list

The CPU socket ID for the region to which this namespace belongs. This can be:

  • Socket 1

  • Socket 2

  • Socket 3

  • Socket 4

Note

 

For UCS M6 B-Series and C-Series servers, only Socket 1 and Socket 2 are supported.

Socket Local DIMM Number drop-down list

The local DIMM number for the region to which this namespace belongs. This can be:

  • The only option avilable for App Direct persistent memory type—Not Applicable

  • The options available for the App Direct Non Interleaved persistent memory type include:

    • Socket Local DIMM No 2

    • Socket Local DIMM No 3

    • Socket Local DIMM No 4

    • Socket Local DIMM No 6

    • Socket Local DIMM No 7

    • Socket Local DIMM No 8

    • Socket Local DIMM No 10

    • Socket Local DIMM No 11

    • Socket Local DIMM No 12

    • Socket Local DIMM No 14

    • Socket Local DIMM No 15

    • Socket Local DIMM No 16

Note

 

The Socket Local DIMM No 3, 7, 11, 14, 15, and 16 are applicable only for UCS M6 B-Series and C-series servers.

Health column

The health status of the persistent memory module.

Status column

Security status of the persistent memory module. The security states can be:

  • Disabled, Unlocked, Frozen, Count Not Expired—Security is disabled, secure passphrase is not configured, the host OS can configure the persistent memory modules and use them, but cannot configure the security of these persistent memory modules, retry count has not expired

  • Disabled, Unlocked, Not Frozen, Count Not Expired—Security is disabled, secure passphrase is not configured, the persistent memory module can be configured, retry count has not expired

  • Enabled, Unlocked, Frozen, Count Not Expired—Security is enabled, persistent memory modules are unlocked, the host OS can configure the persistent memory modules and use them, but cannot configure the security of these persistent memory modules, retry count has not expired

  • Enabled, Locked, Not Frozen, Count Not Expired—Security is enabled, persistent memory modules are locked by using the secure passphrase, the persistent memory module can be configured, retry count has not expired

  • Enabled, Locked, Not Frozen, Count Expired—Security is enabled, persistent memory modules are locked by using the secure passphrase, the persistent memory module can be configured, retry count has expired

Firmware Version column

The firmware version of the persistent memory module.

Total Capacity (GiB) column

The total capacity of the persistent memory module in GiB.

Viewing Persistent Memory Module Properties

Procedure

Step 1

In the Navigation pane, click Equipment.

Step 2

Expand to a server using one of the following paths:

  • For a blade server, expand Equipment > Chassis > Chassis-Number > Servers
  • For a rack-mount server, expand Equipment > Rack Mounts > Servers

Step 3

Select the server for which you want to view persistent memory module properties.

Step 4

In the Work pane, click the Inventory tab and then the Persistent Memory subtab.

Step 5

Click the DIMMS subtab.

Step 6

Select a persistent memory module.

Click on the persistent memory module name. Do not click the Select checkbox for the persistent memory module.

Step 7

Click Info. The Properties dialog box appears with the following information:

Properties area

Name Description

ID field

The identifier for the persistent memory module.

Location field

The slot in which the persistent memory module is installed.

Product Name field

The persistent memory module name.

Socket ID field

The CPU socket ID for the persistent memory module. This can be:

  • Socket 1

  • Socket 2

  • Socket 3

  • Socket 4

Note

 

For UCS M6 B-Series and C-Series servers, only Socket 1 and Socket 2 are supported.

Socket Local DIMM Number field

The local DIMM number for the persistent memory module. This can be:

  • The only option avilable for App Direct persistent memory type—Not Applicable

  • The options available for the App Direct Non Interleaved persistent memory type include:

    • Socket Local DIMM No 2

    • Socket Local DIMM No 3

    • Socket Local DIMM No 4

    • Socket Local DIMM No 6

    • Socket Local DIMM No 7

    • Socket Local DIMM No 8

    • Socket Local DIMM No 10

    • Socket Local DIMM No 11

    • Socket Local DIMM No 12

    • Socket Local DIMM No 14

    • Socket Local DIMM No 15

    • Socket Local DIMM No 16

Note

 

The Socket Local DIMM No 3, 7, 11, 14, 15, and 16 are applicable only for UCS M6 B-Series and C-series servers.

Vendor field

The name of the manufacturer.

PID field

The server model PID.

Revision field

The revision number.

Vendor Serial (SN) field

The serial number assigned by the manufacturer.

Array field

The array containing the persistent memory module.

Bank field

The bank within the array.

Clock (MHz) field

The persistent memory module speed.

Form Factor field

The persistent memory module form factor.

Health State field

The health status of the persistent memory module.

Latency (ns) field

The delay incurred when the server accesses this persistent memory module.

Set field

If this persistent memory module is part of set, this field displays the identifier for the set.

Type field

The persistent memory module type.

Width field

The persistent memory module width.

Capacity (MB) field

The size of the persistent memory module.

Persistent Memory Capacity (GiB) field

The persistent memory capacity of the persistent memory module in GiB.

Total Capacity (GiB) field

The total capacity of the persistent memory module in GiB.

Reserved Capacity field

The reserved capacity of the persistent memory module in GiB.

App Direct Capacity (GiB) field

The App Direct memory capacity of the persistent memory module.

Memory Capacity (GiB) field

The volatile memory capacity of the persistent memory module in GiB.

Security Status field

Security status of the persistent memory module. The security states can be:

  • Disabled, Unlocked, Frozen, Count Not Expired—Security is disabled, secure passphrase is not configured, the host OS can configure the persistent memory modules and use them, but cannot configure the security of these persistent memory modules, retry count has not expired

  • Disabled, Unlocked, Not Frozen, Count Not Expired—Security is disabled, secure passphrase is not configured, the persistent memory module can be configured, retry count has not expired

  • Enabled, Unlocked, Frozen, Count Not Expired—Security is enabled, persistent memory modules are unlocked, the host OS can configure the persistent memory modules and use them, but cannot configure the security of these persistent memory modules, retry count has not expired

  • Enabled, Locked, Not Frozen, Count Not Expired—Security is enabled, persistent memory modules are locked by using the secure passphrase, the persistent memory module can be configured, retry count has not expired

  • Enabled, Locked, Not Frozen, Count Expired—Security is enabled, persistent memory modules are locked by using the secure passphrase, the persistent memory module can be configured, retry count has expired

UID field

The unique hardware ID for the persistent memory module.

Firmware area

Name

Description

Running Version field

The firmware version used by the persistent memory module.

Package Version field

The version of the firmware included in the package.

Startup Version field

The version of the firmware that takes effect the next time that the component reboots.

Activate Status field

This can be one of the following:

  • Ready—Activation succeeded and the component is running the new version.

  • Activating—The system is activating the new firmware version.

  • Failed—The firmware activation failed. For more information, double-click the failed component to view its status properties.

Performing Secure Erase on a Persistent Memory Module

For the secure erase operation, you must provide a secure passphrase when security is enabled. When security is disabled, a secure passphrase is not required for the secure erase operation.

Procedure

Step 1

In the Navigation pane, click Equipment.

Step 2

Expand to a server using one of the following paths:

  • For a blade server, expand Equipment > Chassis > Chassis-Number > Servers
  • For a rack-mount server, expand Equipment > Rack Mounts > Servers

Step 3

Select the server for which you want to securely erase the persistent memory modules.

Step 4

In the Work pane, click the Inventory tab and then the Persistent Memory subtab.

Step 5

Click the DIMMS subtab.

Step 6

Click the Select checkbox for the persistent memory modules that you want to securely erase.

Step 7

Click Secure Erase and then click Yes.

Securely erasing persistent memory modules is a destructive operation, and will result in deletion of region data and namespaces.

Step 8

In the Secure Erase dialog box:

  • If security is enabled, enter the secure passphrase and click OK.
  • If security is not enabled, click OK (empty passphrase).

Unlocking Foreign Persistent Memory Modules

Before you begin

Before you use the following procedure to select the persistent memory modules to be unlocked, and perform the unlock foreign DIMMs operation, ensure that you do the following:

  1. Decommission the server.

  2. Change the persistent memory modules.

  3. Recommission the server.

  4. Associate the server to a service-profile without a persistent memory policy.

  5. Ensure that the server is in the powered-on state, and BIOS POST is completed.

Procedure

Step 1

In the Navigation pane, click Equipment.

Step 2

Expand to a server using one of the following paths:

  • For a blade server, expand Equipment > Chassis > Chassis-Number > Servers
  • For a rack-mount server, expand Equipment > Rack Mounts > Servers

Step 3

Select the server on which you want to unlock foreign persistent memory modules.

Step 4

In the Work pane, click the Inventory tab and then the Persistent Memory subtab.

Step 5

Click the DIMMS subtab.

Step 6

Click the Select checkbox for the foreign persistent memory modules that you want to unlock.

Step 7

Click Unlock Foreign DIMMs.

Step 8

In the dialog box that appears, enter the currently deployed secure passphrase for the foreign persistent memory modules, and click OK.

You must provide the same passphrase that is already deployed on the foreign persistent memory module taken from a different server.

What to do next

  1. Check whether the persistent memory modules get unlocked after the ExecuteActions FSM completes. Now, the persistent memory modules are ready to be used.

  2. Attach a persistent memory policy.

  3. Check whether the associate FSM completes.

Viewing the Persistent Memory Configuration of a Server

You can view the configuration of persistent memory modules on a B-Series, C-Series, or S-Series server.

Procedure

Step 1

In the Navigation pane, click Equipment.

Step 2

Expand to a server using one of the following paths:

  • For a blade server, expand Equipment > Chassis > Chassis-Number > Servers
  • For a rack-mount server, expand Equipment > Rack Mounts > Servers

Step 3

Select the server for which you want to view the persistent memory configuration.

Step 4

In the Work pane, click the Inventory tab and then the Persistent Memory subtab.

Step 5

Click the Configuration subtab. The following information appears:

Table 1. Properties Area

Name

Description

Memory Capacity (GiB) field

The volatile memory capacity of all the persistent memory modules on the server in GiB.

Persistent Memory Capacity (GiB) field

The persistent memory capacity of all the persistent memory modules on the server in GiB.

Reserved Capacity field

The reserved capacity of all the persistent memory modules on the server in GiB.

Total Capacity (GiB) field

The total capacity of all the persistent memory modules on the server in GiB.

Configured Result Error Description field

The errors in the persistent memory configuration of the server.

Config Result field

The result of the persistent memory configuration.

Config State field

The state of the persistent memory configuration.

Security State field

Security status of the persistent memory configuration. The security states can be:

  • Disabled-Frozen—When persistent memory modules are in UCS Managed mode and security is disabled on all persistent memory modules.

  • Disabled—When persistent memory modules are in Host Managed mode and security is disabled on all persistent memory modules.

  • Unlocked-Frozen—When persistent memory modules are in UCS Managed mode and security is enabled on all persistent memory modules.

  • Enabled,Locked—When persistent memory modules are in Host Managed mode and security is enabled on all persistent memory modules.

  • Mixed-State—When some persistent memory modules have security enabled and the rest have security disabled.

Performing Secure Erase on All Persistent Memory Modules on a Server

For the secure erase operation, you must provide a secure passphrase when security is enabled. When security is disabled, a secure passphrase in not required for the secure erase operation.

Procedure

Step 1

In the Navigation pane, click Equipment.

Step 2

Expand to a server using one of the following paths:

  • For a blade server, expand Equipment > Chassis > Chassis-Number > Servers
  • For a rack-mount server, expand Equipment > Rack Mounts > Servers

Step 3

Select the server for which you want to securely erase the persistent memory modules.

Step 4

In the Work pane, click the Inventory tab and then the Persistent Memory subtab.

Step 5

Click the Configuration subtab.

Step 6

Click Secure Erase.

Securely erasing persistent memory modules is a destructive operation, and will result in deletion of all the region data and namespaces on the server.

Viewing the Regions on a Server

You can view the inventory of the regions on a B-Series, C-Series, or S-Series server.

Procedure

Step 1

In the Navigation pane, click Equipment.

Step 2

Expand to a server using one of the following paths:

  • For a blade server, expand Equipment > Chassis > Chassis-Number > Servers
  • For a rack-mount server, expand Equipment > Rack Mounts > Servers

Step 3

Select the server for which you want to view the region inventory.

Step 4

In the Work pane, click the Inventory tab and then the Persistent Memory subtab.

Step 5

Click the Regions subtab. The following information appears:

Name

Description

Id column

The ID of the region.

Socket ID column

The CPU socket ID for the region. This can be:

  • Socket 1

  • Socket 2

  • Socket 3

  • Socket 4

Note

 

For UCS M6 B-Series and C-Series servers, only Socket 1 and Socket 2 are supported.

Socket Local DIMM Number column

The local DIMM number for the region. This can be:

  • The only option avilable for App Direct persistent memory type—Not Applicable

  • The options available for the App Direct Non Interleaved persistent memory type include:

    • Socket Local DIMM No 2

    • Socket Local DIMM No 3

    • Socket Local DIMM No 4

    • Socket Local DIMM No 6

    • Socket Local DIMM No 7

    • Socket Local DIMM No 8

    • Socket Local DIMM No 10

    • Socket Local DIMM No 11

    • Socket Local DIMM No 12

    • Socket Local DIMM No 14

    • Socket Local DIMM No 15

    • Socket Local DIMM No 16

Note

 

The Socket Local DIMM No 3, 7, 11, 14, 15, and 16 are applicable only for UCS M6 B-Series and C-series servers.

DIMM Locator IDs

The locator IDs of the DIMMs in the region.

Persistent Memory Type

The type of persistent memory. This can be one of the following:

  • App Direct—Configures one region for all the persistent memory modules connected to a socket.

  • App Direct Non Interleaved—Configures one region for each persistent memory module.

Total Capacity column

The total capacity of the region in GiB.

Free Capacity column

The available capacity of the region in GiB.

Health Status column

The health status of the region.

Viewing Region Properties

Procedure

Step 1

In the Navigation pane, click Equipment.

Step 2

Expand to a server using one of the following paths:

  • For a blade server, expand Equipment > Chassis > Chassis-Number > Servers
  • For a rack-mount server, expand Equipment > Rack Mounts > Servers

Step 3

Select the server for which you want to view persistent memory module properties.

Step 4

In the Work pane, click the Inventory tab and then the Persistent Memory subtab.

Step 5

Click the Regions subtab.

Step 6

Select a region.

Step 7

Click Info. The Properties dialog box appears with the following information:

Name Description

ID field

The identifier for the region.

Socket ID field

The CPU socket ID for the region.

Local DIMM Slot ID field

The local DIMM slot ID for the region.

DIMM Locator IDs field

The locator IDs of the DIMMs in the region.

Operational Mode field

The persistent memory type of the region.

Total Capacity (GiB) field

The total capacity of the region in GiB.

Free Capacity (GiB) field

The available capacity of the region in GiB.

Health State field

The health status of the region.

Interleaved Set ID field

The ID of the interleaved set for the region.

Viewing the Namespaces on a Server

You can view the inventory of the namespaces on a B-Series, C-Series, or S-Series server.

Procedure

Step 1

In the Navigation pane, click Equipment.

Step 2

Expand to a server using one of the following paths:

  • For a blade server, expand Equipment > Chassis > Chassis-Number > Servers
  • For a rack-mount server, expand Equipment > Rack Mounts > Servers

Step 3

Select the server for which you want to view the namespace inventory.

Step 4

In the Work pane, click the Inventory tab and then the Persistent Memory subtab.

Step 5

Click the Namespace subtab. The following information appears:

Name

Description

Name column

The name of the namespace.

Mode column

The mode in which the namespace is created. This can be:

  • Raw

  • Block

Capacity(GiB) column

The memory capacity of the namespace in GiBs.

Health Status column

The health status of the namespace.

Viewing Namespace Properties

Procedure

Step 1

In the Navigation pane, click Equipment.

Step 2

Expand to a server using one of the following paths:

  • For a blade server, expand Equipment > Chassis > Chassis-Number > Servers
  • For a rack-mount server, expand Equipment > Rack Mounts > Servers

Step 3

Select the server for which you want to view namespace properties.

Step 4

In the Work pane, click the Inventory tab and then the Persistent Memory subtab.

Step 5

Click the Namespace subtab.

Step 6

Select a namespace within a region.

Step 7

Click Info. The Properties dialog box appears with the following information:

Name Description

Name field

The name of the namespace.

Capacity (GiB) field

The total capacity of the namespace in GiB.

Health Status field

The health status of the namespace.

Label Version field

The label version of the namespace.

Operational Mode field

The persistent memory type of the namespace.

UUID field

The unique hardware ID of the persistent memory module on which the namespace is created.

Disassociating the Service Profile and the Scrub Policy with Persistent Memory Scrub Selected

Disassociating the service profile and the scrub policy, which has the persistent memory scrub option selected will result in deletion of all regions and namespaces and its data in all the persistent memory modules. Security will be disabled, if it is already enabled. The following procedure describes how to disassociate a service profile and a scrub policy.

Procedure

Step 1

In the Navigation pane, click Servers.

Step 2

Expand Server > Service Profiles

Step 3

Select the service profile.

Step 4

In the Work pane, click the Policies tab.

Step 5

In the Policies area, expand Scrub Policy.

Step 6

From the Scrub Policy drop-down list, select a scrub policy with the persistent memory scrub option enabled.

Step 7

Click Save Changes.

The scrub policy now gets associated with the service profile.

Step 8

Right-click the service profile and select Disassociate Service Profile.

Step 9

In the Disassociate Service Profile dialog box, click Yes to confirm that you want to disassociate the service profile.

On UCS M5, M6 B-Series and C-Series servers: Regions and namespaces will be deleted after successful disassociation.

On UCS M5 S-Series servers: Namespaces will be deleted after successful disassociation.

Resetting a Server to Factory Defaults With Persistent Memory Scrub Selected

You can reset a server to its factory settings. By default, the factory reset operation does not affect storage drives, persistent memory modules, and flexflash drives. This is to prevent any loss of data. However, you can choose to reset these devices to a known state as well.


Important

Resetting storage devices will result in loss of data.

Perform the following procedure to reset the server to factory default settings, and delete persistent memory configuration and data.

Procedure

Step 1

In the Navigation pane, click Equipment.

Step 2

Expand Equipment > Chassis > Chassis Number > Servers.

Step 3

Choose the server that you want to reset.

Step 4

In the Work pane, click the General tab.

Step 5

In the Actions area, click Server Maintenance.

Step 6

Select the Reset to Factory Default checkbox, and click OK.

Step 7

In the Maintenance Server dialog box, select the Persistent Memory Scrub checkbox, and click OK.

The server settings are set to factory default, persistent memory configuration and data are deleted.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco