Can iSCSI Targets be Renamed on an EqualLogic PS Series Storage Area Network?

I received a tweet from someone a few days ago asking if it was possible to rename an iSCSI target on an EqualLogic PS Series Storage Area Network (SAN). I wasn’t sure, but it was interesting enough to research and determine if it was possible or not.

Based on a screenshot provided by this person, they wanted to change the default iSCSI target name prefix so new volumes that are created have a different target prefix. It’s possible to change this setting using PowerShell, but not the GUI:

Even though this setting change shows up in the GUI, it doesn’t have any effect when creating a new volume. You still end up with the original default iSCSI target name.

Ok, but what about changing the iSCSI target name on an existing volume?

After looking at the PowerShell cmdlet parameters for Set-EQLVolume and looking in the GUI, it doesn’t appear that an iSCSI target can be renamed. The alias can be changed, but that doesn’t accomplish the same thing as renaming the iSCSI target.

Even when creating a new volume, there’s no way in PowerShell or using the GUI to specify a custom iSCSI target name. It appears to be derived from the volume name. It’s possible to rename the volume after it’s created, but you’re stuck with the original iSCSI target name. My guess is this is the reason you would want to rename the iSCSI target.

The only way to change the iSCSI target name on an EqualLogic PS Series SAN that I’ve found is to clone the volume to the name you want for the volume and iSCSI target.

Take the volume offline in the OS first:

Then disconnect from the iSCSI target by using the iSCSI Control Panel:

Open PowerShell and connect to the SAN:

The clone process does not copy the description, ACL’s, snapshot schedule, or replication settings. Here are the settings on the original volume that we want to replicate to the new one with the exception of the volume name and iSCSI target name:

Clone the volume using a PowerShell script similar to the following one. The current volume name is “mikefrobbins” and I’m cloning it to a volume named “mikefrobbins2” along with copying the description, ACL’s, and snapshot settings from the original volume, all with PowerShell. Each of these steps would be a manually process through the GUI. Always start out by taking a snapshot of the volume before making any changes to it. The last thing this script does is remove the original volume’s ACL’s and set it offline to make sure nothing can access it while keeping it around for a few days just in case an old snapshot is needed.

The original volume should be removed at a later date. I covered removing volumes in the “Use PowerShell to Manage an EqualLogic SAN” guest blog that I wrote for the Hey, Scripting Guy! Blog a few weeks ago.

Now to verify the settings have been copied to the new volume that were previously on the old one. I’m running the same script as before except with $VolName = ‘mikefrobbins2’:

From the iSCSI Control Panel, connect to the new iSCSI target:

Remove the old iSCSI target from the list on the “Favorite Targets” tab:

Verify the volume is online in the OS and that it has the correct drive letter assigned to it:

From the iSCSI control panel, click the “Auto Configure” button on the “Volume and Devices” tab so the correct drive letter in the OS is mapped to the iSCSI target each time the server is restarted:

Disconnect from the SAN when you’re finished:

µ

1 Comment

  1. Nahuel

    Hi, My name is Nahuel i From Argentina.

    A few days ago I am trying to configure a volume to add more of a Target IQN. I can generate the volume but not how to connect with my target host. I run the following:

    “New-VolumeName EqlVolume-TEST-10000-StoragePoolName VolumeSizeMB EQL3-Pool-100-AccessType SnapshotReservePercent LoadBalance read_write-yes-yes Onlinestatus-online-AllowMultipleInitiators VolumeDescription Test_Descripcion-90-SnapshotDeletionPolicy SnapshotReserveWarnPercent delete_oldest-yes-ThinProvisionMinReservePercent ThinProvision ThinProvisionWarningPercent60-ThinProvisionMaxGrowPercent 10-100 ‘

    But the volume is “NO ACCESS”. I have 4 Server Vmware target.

    Thank you so much

    Reply

Leave a Reply

%d bloggers like this: