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.
For some Windows environments, you could use Windows PowerShell to retrieve the WWN.
For example:
PS C:\> get-disk -number 2 | select uniqueid uniqueid -------- 6006016016504100C91E025B7C58F68B
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.
$sudo /sbin/iscsid force-start &
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>
$sudo /sbin/iscsiadm -m discovery -t st -p <IP of iSCSI interface>
$sudo /sbin/iscsiadm -m node --login
>ls /dev/sd* /dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdc /dev/sdd
$ 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
