Rename PowerFlex SDCs with SCLI for a Clearer ESXi Inventory

This guide shows how to change the display name associated with a Dell PowerFlex Storage Data Client (SDC) by using SCLI. In the example, two ESXi SDC records are listed as N/A; the goal is to give each record a name that is easier to recognize in the PowerFlex inventory.

The examples use SDCs reporting version 4.5.0 in a lab. Renaming an SDC changes its name in the PowerFlex system; it does not rename the ESXi host, change DNS, or update the vCenter inventory. Use the SCLI reference and command syntax that match the PowerFlex release managing the SDCs.

If you still need to install the client on an ESXi host, see Connecting VMware ESXi to PowerFlex: A Step-by-Step SDC Installation Guide.

For an overview of PowerFlex components and architecture, see Getting Started with Dell PowerFlex: Architecture and Key Components.

Important: Before renaming an entry, query the SDC inventory and identify the target by its GUID. Cross-check the GUID against the expected IP addresses and operating-system type. Do not choose a record based only on a friendly name, a partial IP match, or the order in which records appear. If the SDC is disconnected or the inventory shows stale MDM addresses, investigate that state and confirm that you are connected to the intended PowerFlex system before making the change:

scli --query_all_sdc

Step-by-step

1- In this case, we have added both SDCs and the Name is “N/A.” So, based on it, we want to change it to a friendly name.

The first SDC has the IPs “192.168.155.213,192.168.156.213“:

scli --query_all_sdc | grep -i -A4 "192.168.155.213,192.168.156.213"

SDC ID: 997fd4f300000010 Name: N/A IPs: 192.168.155.213,192.168.156.213 State: Connected GUID: 49D88B62-5237-4EF8-97E4-75B0CFD31A42  OS Type: ESX Loaded Version: 4.5.0 Installed Version: 4.5.0
    Agent status: disabled MDM IP addresses: stale Reboot safe: no
    Reads:  0 IOPS 0 Bytes per second
    Writes: 0 IOPS 0 Bytes per second

The second SDC has the IPs “192.168.155.214,192.168.156.214“:

scli --query_all_sdc | grep -i -A3 "192.168.155.214,192.168.156.214"

SDC ID: 997fd4f400000011 Name: N/A IPs: 192.168.155.214,192.168.156.214 State: Connected GUID: C6BADE3A-75CC-42DA-9678-EE7FA5B8A353  OS Type: ESX Loaded Version: 4.5.0 Installed Version: 4.5.0
    Agent status: disabled MDM IP addresses: stale Reboot safe: no
    Reads:  0 IOPS 0 Bytes per second
    Writes: 0 IOPS 0 Bytes per second

2- Changing the name for each one:

192.168.155.213,192.168.156.213 –> ESXI06
192.168.155.214,192.168.156.214 –> ESXI07

The GUID uniquely identifies the SDC record that SCLI will rename. Compare each GUID with the inventory output immediately before running the command. The names below are examples; retain the GUIDs only if they match the intended SDCs in your own system:

scli --rename_host --sdc_guid 49D88B62-5237-4EF8-97E4-75B0CFD31A42 --new_name ESXI06

scli --rename_host --sdc_guid C6BADE3A-75CC-42DA-9678-EE7FA5B8A353 --new_name ESXI07

If SCLI reports an error, do not retry with a different GUID or name until you have checked the message and queried the inventory again. Confirm that the GUID still belongs to the intended SDC and that the command is being sent to the correct PowerFlex system. A rename operation does not repair connectivity or stale MDM-address information.

Note: The current Dell PowerFlex 4.5.x CLI reference documents rename_host, not rename_sdc. Check if it can be your case!

3- Afterward, checking the name:

scli --query_all_sdc | grep -i -A3 "192.168.155.213,192.168.156.213"
SDC ID: 997fd4f300000010 Name: ESXI06 IPs: 192.168.155.213,192.168.156.213 State: Connected GUID: 49D88B62-5237-4EF8-97E4-75B0CFD31A42  OS Type: ESX Loaded Version: 4.5.0 Installed Version: 4.5.0
    Agent status: disabled MDM IP addresses: stale Reboot safe: no
    Reads:  0 IOPS 0 Bytes per second
    Writes: 0 IOPS 0 Bytes per second


scli --query_all_sdc | grep -i -A3 "192.168.155.214,192.168.156.214"
SDC ID: 997fd4f400000011 Name: ESXI07 IPs: 192.168.155.214,192.168.156.214 State: Connected GUID: C6BADE3A-75CC-42DA-9678-EE7FA5B8A353  OS Type: ESX Loaded Version: 4.5.0 Installed Version: 4.5.0
    Agent status: disabled MDM IP addresses: stale Reboot safe: no
    Reads:  0 IOPS 0 Bytes per second
    Writes: 0 IOPS 0 Bytes per second

Note: After the rename, run the same queries again and verify that the Name field contains the expected value and that the GUID still identifies the intended SDC.

Final Thoughts

A clear SDC name makes the PowerFlex host list easier to interpret, but the GUID remains the reliable identifier for this operation. After renaming, query the SDC inventory again and confirm that the Name field changed for the intended GUID while the GUID and IP addresses still match the same record.

The sample output also shows MDM IP addresses: stale and Reboot safe: no. These are separate status indicators, not evidence that the rename changed the SDC’s connectivity or reboot state. Do not treat Reboot safe: no as approval to reboot the host; investigate that warning using the guidance for the specific PowerFlex release before any maintenance or restart.

External References