• - [Instructor] In the terminal, type in sudo yum

install -y targetcli and hit Enter. Type in your

password if prompted. To ensure that the
changes made in targetcli are persistent, we
need to start and enable the target service. To
start the service, type in clear, and then type
in sudo systemctl start target and hit Enter.
And to make this persistent, bring your line
back and change start to enable. Your line
should read sudo systemctl enable target and
• - [Instructor] In Enterprise Linux 6, the term
backing store was used for mappings created
in the target. These are now called storage
objects. In Enterprise Linux 7, we use the term
backstore to reference different types of
backing devices, such as block devices and
logical volumes. Backstores supported by the
LIO iSCSI target include FILEIO, BLOCK, PSCSI,
and memory copy RAMdisks. FILEIO
backstores are Linux file-backed storage.
• Instructor] Previously in this chapter, we
created a fileio backstore. Let's verify this
before moving on. Make sure your rhhost1
VM is booted and you're logged in. In a
terminal, run targetcli using sudo. Type in
sudo targetcli, and hit enter. Type in your
password if prompted. If it's already running,
you can skip this step. Now type in ls to verify
that the backstore exists. Type in ls and hit
enter. We see the fileio-based backstore, but
we created a back store, a target, and a LUN.
Now lets create an access control list. Be sure
you're logged into your rhhost1 VM and you
have a terminal open with targetcli running as
root. You haven't done this. Type in sudo
space targetcli and hit enter. Let's also verify
our progress. Go to your targetcli root by
typing in cd space slash and hit enter. Then
type in ls. You should see our file io back store
named file1. You should also see a target
named iqn.2018-04.com.localnet:filedisk1
which has a LUN and a portal. The latter was
auto generated because we're using a version
of Enterprise Linux newer than 7.1. Now let's
• - [Instructor] Before our target is fully
functional, we'll need to allow traffic through
the firewall. Let's make sure our target service
is answering on port 3260 first. We'll use
natstat for this. Type into a terminal sudo
space netstat space dash a t and hit enter.
Type in your password if prompted. Here we
can see that the iscsi target is listening. If you
want to see the port numbers listening on,
add dash n to netstat. So bring your line back,
• Instructor] For this video you need to have
your rhhost1 VM booted. You should also have
your rhhost2 VM booted up and you should
be logged in with a terminal open. To set up
our initiator we need to start by editing an
iscsi config file. Type in sudo space vi space
/etc/iscsi/intiatorname.iscsi and hit Enter.
Change the initiator name to iqn.2018-
04.com.localnet:client1, which we set up in a
previous video when we configured our access
• auth method line and uncomment it. We'll
also want to make sure it says CHAP. Now look
below it and find the username line.
Uncomment it and change the user to user1.
Next, below that is the password line.
Uncomment it and change it to the password
you chose. In my case I chose the word
password so I'll leave it alone. Now press
escape :x! to save it. Since we've changed our
iqn settings in our initiator we will want to
• Now that we have our drive exported from
rhhost1, and accessible in rhhost2, we will put
a partition on it, format it, and mount it by a
UUID number. In order to do this, make sure
your rhhost2 VM is booted and you're logged
in. Also make sure your rhhost1 VM is running
as well. Let's also verify that we still have
access to iscsi drive. In a terminal, type sudo
lsblk -- scsi and hit Enter. If you see the iscsi
device, you can proceed. If you do not see it,
• - [Instructor] This challenge concerns iSCSI
targets and initiators. For this challenge, you'll
need to create a 500 megabyte file IO
backstore called challenge1. Be sure write
back for the backstore is turned off. Create a
target named iqn.2019-
06.com.localnet:challenge1. Create an ACL
named iqn.2019-06.com.localnet:rhhost2. Set
up a user and password for the ACL. Configure
the initiator on rhhost2. Be sure the initiator
• soft chiming) (upbeat music) - [Instructor] To
satisfy the challenge objectives we first have
to install software on rhhost1, we'll install the
targetcli package by typing in sudo space yum
space install space dash y space targetcli and
hit Enter. Now let's start the service, type in
sudo space systemctl space start space target
and hit Enter and bring your line back and
change start to enable to make it persistent.
Now let's create a directory for our file IO
 CpterH 4
• 00:01/01:52CourseOverview Transcript View
Offline- [Instructor] For this exercise, be sure
your logged in to RH host one as user one, and
have a terminal open. The chrony server and
client should already be installed by default.
But to be sure, type into a terminal sudo space
yum space install space dash y space chrony,
and hit enter. This will not hurt anything if it's
already installed. After making sure chrony is
installed, we need to make sure the service is