Was this content helpful?
How could we make this article more helpful?
Small Computer System Interface (SCSI) is a widely used protocol for controlling direct-attached storage devices. Internet SCSI (iSCSI) uses the SCSI protocol on network volumes. iSCSI works on top of the Transport Control Protocol (TCP) and allows SCSI commands to be sent through a local area network (LAN), wide area network (WAN), or the internet.
Your iSCSI network requires four components:
Data network—iSCSI requires an IP-based network for data transport between systems with initiators (servers) and targets (storage volumes or arrays).
Management network—To configure the applicable iSCSI ports on Lyve Mobile Rackmount Receiver, a Windows or Mac computer installed with the Lyve Client Software app must be able to access the same management network connected to an Ethernet management port on the back of Rackmount Receiver. Make sure to use the Ethernet management port for the slot in which the Lyve Mobile Array device is inserted.
iSCSI target—The target is a storage volume or array connected to the network. In the following instructions, the iSCSI target is a volume in a Lyve Mobile Array inserted in a Lyve Mobile Rackmount Receiver.
iSCSI initiator—The initiator is the software component residing on a server that is configured to connect to an iSCSI target. By using an iSCSI initiator, target volumes can be mounted on a server as if they were local volumes.
Assign or obtain the following:
The Lyve Client app relies on the Service Location Protocol (SLP) to discover Lyve Mobile devices on the network. For automatic detection, the following is required:
If your company's IT policies prevent SLP network broadcasting, you can use other methods for detecting the device in Lyve Client. See Alternative methods for device detection below.
Before beginning the configuration, make sure a Windows or Mac computer that will run the Lyve Client Software app can access the same management network connected to the Ethernet management port on the back of Rackmount Receiver.
The LED on the device inserted in Lyve Mobile Rackmount Receiver blinks white during the boot process and will turn one of two colors, depending on your device's security settings:
Solid orange—Indicates the device is ready to be unlocked and is awaiting security credentials.
Solid green—Device is unlocked and ready for use.
If your network environment supports a Multipath I/O (MPIO) framework, ensure that MPIO is installed before configuring iSCSI.
To enable MPIO:
sudo mpathconf --enable --with_multipathd y
Install the Lyve Client app on a Windows or Mac computer connected to the management network. Links to the installer can be found on Lyve Management Portal:
You can also download Lyve Client installers from the support page at www.seagate.com/support/lyve-client.
Open the Lyve Client app.
Lyve Client will automatically unlock the device if the management computer was connected to Lyve Mobile Array in the past and is still authorized for security. If the management computer has never unlocked the device, you will need to enter your Lyve Management Portal username and password in the Lyve Client app.
Once Lyve Client has validated permissions for the device connected to the computer, the LED on the device turns solid green. The device is unlocked and ready for use.
Activity—An iSCSI Setup notification informs you that a setup is required.
Devices—The status indicator on the Device card informs you that a setup is required.
yum install iscsi-initiator-utils
iscsiadm -m discovery -t st -p IP address
where IP address is the Rackmount Receiver iSCSI port IP address, for example:
iscsiadm -m discovery -t st -p 192.168.99.100
Example output |
---|
192.168.99.100:3260,1 iqn.1995-03.com.dothill:01.array.000000000000-00000000.a 192.168.99.101:3260,2 iqn.1995-03.com.dothill:01.array.000000000000-00000000.a |
iscsiadm -m node -T IQN –l
where IQN is an iSCSI qualified name, for example:
sudo iscsiadm -m node -T iqn.1995-03.com.dothill:01.array.000000000000-00000000.a –l
The IQN can be found in the output from the previous discovery command.
Example output |
---|
Logging in to [iface: default, target: iqn.1995-03.com.dothill:01.array.000000000000-00000000.a, portal: 192.168.99.100,3260] Logging in to [iface: default, target: iqn.1995-03.com.dothill:01.array.000000000000-00000000.a, portal: 192.168.99.101,3260] Login to [iface: default, target: iqn.1995-03.com.dothill:01.array.000000000000-00000000.a, portal: 192.168.99.100,3260] successful. Login to [iface: default, target: iqn.1995-03.com.dothill:01.array.000000000000-00000000.a, portal: 192.168.99.101,3260] successful. |
sudo mkdir /mnt/SEAGATE
sudo blkid
Example output |
---|
/dev/nvme0n1p1: UUID="40AA-21FC" TYPE="vfat" PARTUUID="e97d9f0d-c95d-4afd-a790-8abc41474070" /dev/nvme0n1p2: UUID="769fcf3e-1886-4cbb-b1f3-23745d390c96" TYPE="ext4" PARTUUID="8f8edcee-3f56-411a-a227-2bba1463bc25" /dev/nvme0n1p3: UUID="Z5wnnv-zSCu-cGD0-9ffc-37n1-1cKE-4usCIb" TYPE="LVM2_member" PARTUUID="b8f4bd59-c296-4e4d-9ad0-fc4cbb98a69f" /dev/mapper/ubuntu--vg-ubuntu--lv: UUID="882c9573-ea5e-4b8f-bb54-1aec9b1e8dea" TYPE="ext4" /dev/loop0: TYPE="squashfs" /dev/loop1: TYPE="squashfs" /dev/loop2: TYPE="squashfs" /dev/sdc2: LABEL="LYVE" UUID="22A6-E95E" TYPE="exfat" PARTLABEL="Basic data partition" PARTUUID="522a0547-f77f-4679-ae8a-2ded5b651f65" /dev/sdb2: LABEL="LYVE" UUID="22A6-E95E" TYPE="exfat" PARTLABEL="Basic data partition" PARTUUID="522a0547-f77f-4679-ae8a-2ded5b651f65" /dev/mapper/mpatha-part2: LABEL="LYVE" UUID="22A6-E95E" TYPE="exfat" PARTLABEL="Basic data partition" PARTUUID="522a0547-f77f-4679-ae8a-2ded5b651f65" /dev/sde2: LABEL="LYVE" UUID="22A6-E95E" TYPE="exfat" PARTLABEL="Basic data partition" PARTUUID="522a0547-f77f-4679-ae8a-2ded5b651f65" /dev/sdd2: LABEL="LYVE" UUID="22A6-E95E" TYPE="exfat" PARTLABEL="Basic data partition" PARTUUID="522a0547-f77f-4679-ae8a-2ded5b651f65" /dev/sdc1: PARTLABEL="Microsoft reserved partition" PARTUUID="78b2177e-c5a1-4b1f-8db3-6350ae11f05a" /dev/sdb1: PARTLABEL="Microsoft reserved partition" PARTUUID="78b2177e-c5a1-4b1f-8db3-6350ae11f05a" /dev/mapper/mpatha-part1: PARTLABEL="Microsoft reserved partition" PARTUUID="78b2177e-c5a1-4b1f-8db3-6350ae11f05a" /dev/mapper/mpatha: PTUUID="25a51dc7-9ffc-4000-b1dd-e7b9bd81a375" PTTYPE="gpt" /dev/sde1: PARTLABEL="Microsoft reserved partition" PARTUUID="78b2177e-c5a1-4b1f-8db3-6350ae11f05a" /dev/sdd1: PARTLABEL="Microsoft reserved partition" PARTUUID="78b2177e-c5a1-4b1f-8db3-6350ae11f05a" |
sudo mkfs.ext4 -L LYVE /dev/disk/by-uuid/unique ID
where unique ID is the UUID for the Lyve disk listed in the blkid output, for example:
sudo mkfs.ext4 -L LYVE /dev/disk/by-uuid/22A6-E95E
Example output |
---|
Creating filesystem with 23413075456 4k blocks and 1463318528 inodes Filesystem UUID: b2fc70de-a95e-43ef-9008-c8ec4a5a12c6 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000, 214990848, 512000000, 550731776, 644972544, 1934917632, 2560000000, 3855122432, 5804752896, 12800000000, 17414258688 Allocating group tables: 0/714511 658404/714511 done Writing inode tables: 0/714511 done Creating journal (262144 blocks): done Writing superblocks and filesystem accounting information: 0/714511 28/714511 done |
sudo vi /etc/fstab
# SEAGATE iSCSI device
/dev/disk/by-uuid/unique ID /mnt/SEAGATE ext4 _netdev 0 1
where unique ID is the UUID for the Lyve disk listed in the blkid output, for example:
/dev/disk/by-uuid/b2fc70de-a95e-43ef-9008-c8ec4a5a12c6 /mnt/SEAGATE ext4 _netdev 0 1
Mount the drive by entering the following:
sudo mount –a
Assign access permissions by entering the following:
sudo chmod permission /mnt/SEAGATE
where permission is the desired chmod setting in absolute or symbolic mode, for example:
sudo chmod 777 /mnt/SEAGATE
If your console hangs on the network configuration, you may need to add the following command to each interface in the IP configuration file:
(00-installer-config.yaml) optional: true