Skip to main content

Dell EMC Unity™ Family Third-Party System Migration using SAN Copy Pull User Guide

PDF

Retrieving Host LUN World Wide Names (WWNs)

If a third-party system does not expose host LUN WWNs through either a UI or CLI, you need to be able to retrieve the information for use during the migration process.

This section contains examples for how to find source LUN WWN information. There may be other ways of finding the information not documented in this guide.

Windows environment example

For some Windows environments, you could use Windows PowerShell to retrieve the WWN.

NOTE The Windows PowerShell get-disk command is not available in all Windows systems, such as for systems earlier than 2012.

For example:

PS C:\> get-disk -number 2 | select uniqueid

uniqueid
--------
6006016016504100C91E025B7C58F68B

Linux environment example

For Linux environments, there are packages available that contain commands for finding LUN WWN information. The example that follows describes an open source package that can be used to send commands to a third-party system.

  1. To use the example open source package described in this procedure, you will need a Linux system (independent of the Unity system that is being migrated to) that is in the same Ethernet network as the source third-party system.
  2. On the Linux system, install open-iscsi either using a package manager, or from https://github.com/open-iscsi/open-iscsi.
  3. Build and install sg_utils to send SCSI commands to the device.

    https://github.com/hreinecke/sg3_utils

  4. Run the open-iscsi deamon.

    $sudo /sbin/iscsid force-start &

  5. To configure the Linux system as a host on the storage array, you need the iSCSI IQN which is found at:
    sudo cat /etc/iscsi/initiatorname.iscsi 
    ##
    ## /etc/iscsi/iscsi.initiatorname
    ##
    ## Default iSCSI Initiatorname.
    ##
    ## DO NOT EDIT OR REMOVE THIS FILE!
    ## If you remove this file, the iSCSI daemon will not start.
    ## If you change the InitiatorName, existing access control lists
    ## may reject this initiator.  The InitiatorName must be unique
    ## for each iSCSI initiator.  Do NOT duplicate iSCSI InitiatorNames.
    InitiatorName=<initiator_name>
  6. Discover iSCSI targets by using an IP address:

    $sudo /sbin/iscsiadm -m discovery -t st -p <IP of iSCSI interface>

  7. Log in to iSCSI targets, and also mount LUNs to which the Linux host has access.

    $sudo /sbin/iscsiadm -m node --login

  8. Display the mount LUNs.
    >ls /dev/sd*
    /dev/sda  /dev/sda1  /dev/sdb  /dev/sdb1  /dev/sdc  /dev/sdd
  9. Run the sg3_utils command to get device information.
    $ sudo sg_vpd -p di /dev/sdc
    
    Device Identification VPD page:
      Addressed logical unit:
        designator type: NAA,  code set: Binary
          0x6006016005603c0034fe065b271f46de
        designator type: vendor specific [0x0],  code set: Binary
          vendor specific:
    00     00 00 00 00 00 00 00 00  00 15 00 00 00 00 00 00    ................
      Target port:
        designator type: Relative target port,  code set: Binary
          Relative target port: 0x3
        designator type: Target port group,  code set: Binary
          Target port group: 0x2

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\