ESX Iscsi tuto for ESOS

[Hervé Le Moal]

Hi all,

I'm a real noob with ESOS and iscsi in general...

Do you know if it exists any tutorial to start configuring ESOS with no pain ;) ?

I have already tested Freenas with ESX with success but I'm little bit lost with ESOS.

Is there any walkthrough somewhere ?

Kind regards

Hervé

[Marc Smith]

Hi,

Yes, I really need to get a ESOS "quick start guide" created -- just
need to find the time! A while back someone had asked this same
question, so I wrote some quick steps in that email:

Here is a quick flow to get you started (in order, assuming a
single-head setup):
- Create a ESOS USB flash drive.
- Use the ESOS USB drive in your server, boot from USB, boot into ESOS.
- At first boot, change the root password, set timezone, date/time,
and NTP server (if using).
- Configure your network interface(s), host name, etc.
- Configure your "back-end storage" -- this would be using hardware
RAID, or maybe using software RAID, or straight LVM on the raw disks.
Or maybe using RAID and then LVM on top of it, or you could even use a
file system (eg, XFS) on top of the RAID device and create "virtual
disk files" (basically using regular files as virtual disks and
present those to initiators).
- For iSCSI, you'll need to add an iSCSI target interface (just one is
probably fine). Do this in the targets menu, add iSCSI target, default
name is fine (if you like).
- Then enable the iSCSI target (targets menu).
- Next you'll want to create a host "security group" -- this is like
LUN groups, server groups, etc. as used on other disk array systems.
Create a group on the iSCSI target you created above, then add
initiators to group (these will be the IQN's from the
servers/initiators that you want to present the storage to).
- Next you need to create a "device" -- these are part of the mapping
from back-end storage to LUN's. I'd go with vdisk_blockio if using
hardware/software RAID, LVM, etc. and if you're using virtual disk
files on a file system, use vdisk_fileio. The defaults in the SCST
device dialog should be fine.
- Finally, you'll map the SCST device you created in the step above to
a LUN. Do this in the devices menu, I'd add a LUN 0 (most initiators
expect this, so if you only have one, use LUN 0).

That should be about it in a nutshell... the sessions should show up.
You may need to scan from the initiator side. If you don't get any
connectivity, ensure you have a LUN 0 and that you have the initiator
names entered correctly.

Let us know if you have any trouble or questions, we're happy to help.


--Marc

> --
> You received this message because you are subscribed to the Google Groups
> "esos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to esos-users+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Hervé Le Moal]

Thanks Marc,

what a quick answer !

I'll test that today, and make a feedback,

Thanks again, regards

Hervé Le Moal | Product Engineer Performance Vision 88-90 Boulevard de Sébastopol, 75003 Paris p: +33 (0)1 78 09 07 07 | m: +33 (0)6 69 78 11 56  e: herve....@performancevision.com

> email to esos-users+unsubscribe@googlegroups.com.

> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "esos-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to esos-users+unsubscribe@googlegroups.com.

[Hervé Le Moal]

Hi Marc,

just tested and wasn't more succesful ...

Some more details :

- ESOS is installed on a Dell R730 server with hardware RAID controller.

- A raid volume is built from the RAID interface (2x1.9T SSD in RAID0)

- scst.conf :

 Automatically generated by SCST Configurator v3.0.2.

# Non-key attributes

max_tasklet_cmd 10

setup_id 0x0

threads 28

HANDLER vdisk_blockio {

        DEVICE esos-raid0 {

                filename /dev/disk-by-id/LUN_NAA-61866da07f8a54001ff53b13063ffe7f

                # Non-key attributes

                blocksize 512

                nv_cache 0

                pr_file_name /var/lib/scst/pr/esos-raid0

                prod_id esos-raid0

                prod_rev_lvl " 302"

                read_only 0

                removable 0

                rotational 1

                t10_dev_id 6600c86e-esos-raid0

                t10_vend_id SCST_BIO

                thin_provisioned 0

                threads_num 1

                threads_pool_type per_initiator

                tst 1

                usn 6600c86e

                vend_specific_id 6600c86e-esos-raid0

                write_through 0

        }

}

TARGET_DRIVER iscsi {

        enabled 1

        TARGET iqn.2016-12.esos.localhost:7f44f {

                enabled 1

                rel_tgt_id 4

                # Non-key attributes

                DataDigest None

                FirstBurstLength 65536

                HeaderDigest None

                ImmediateData Yes

                InitialR2T No

                MaxBurstLength 1048576

                MaxOutstandingR2T 32

                MaxRecvDataSegmentLength 1048576

                MaxSessions 0

                MaxXmitDataSegmentLength 1048576

                NopInInterval 30

                NopInTimeout 30

                QueuedCommands 32

                RDMAExtensions Yes

                RspTimeout 90

                addr_method PERIPHERAL

                black_hole 0

                cpu_mask ffffffff,ffffffff

                io_grouping_type auto

                per_portal_acl 0

                GROUP esos-raid0 {

                        LUN 0 esos-raid0 {

                                # Non-key attributes

                                read_only 0

                        }

                        INITIATOR esos-raid0

                        # Non-key attributes

                        addr_method PERIPHERAL

                        black_hole 0

                        cpu_mask ffffffff,ffffffff

                        io_grouping_type auto

                }

        }

}

- I've done a network capture between ESX and ESOS during ESX storage discover (file iscsi_esos.pcap attached)

Don't hesitate if you need more info,

Thanks for your help

[Hervé Le Moal]

Just another information :

Esos server is connected by 10G Fiber network card (Intel ixgbe) but it seems not to be a problem ( communication seems ok as shown in the pcap file)

[Marc Smith]

Hi,

Everything looks correct, except this line:

INITIATOR esos-raid0


The "esos-raid0" value (initiator name) should be an iSCSI IQN like
"iqn.1998-01.com.vmware:esx001-0badb9cf". You get these from the ESXi
side for your hosts. Or if you did a scan/login to the portal from
ESXi, they should show up as sessions (with no mapped LUNs) or look in
/var/log/kern.log for the initiator names there so you can copy/paste.

If that doesn't get it for you, please post the /var/log/kern.log file
so we can see if anything is happening.


--Marc

> --
> You received this message because you are subscribed to the Google Groups
> "esos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to esos-users+...@googlegroups.com.

[Hervé Le Moal]

Hi Marc,

I've changed config :

I've grabbed the initiator name in vmware and added it to ESOS config:

[root@localhost ~]# cat /etc/scst.conf 

# Automatically generated by SCST Configurator v3.0.2.

INITIATOR iqn.1998-01.com.vmware:569396ed-adc9-bd29-e7a0-246e96058a68-503e

# Non-key attributes

addr_method PERIPHERAL

black_hole 0

cpu_mask ffffffff,ffffffff

io_grouping_type auto

}

}

}

I've re-done a discover from vmware but it's still the same, no device seen.

Please find attached the related pcap taken during the discover.

Regards

[Marc Smith]

Can you post the /var/log/kern.log file from the ESOS side?

Marc

[Hervé Le Moal]

kern.log attached.

[Marc Smith]

Hi,

I don't see any evidence that there is anything happening with iSCSI
sessions at the SCST level... can you try the basic iSCSI
troubleshooting steps from VMware and see how that goes:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1008083


--Marc


On Thu, Dec 29, 2016 at 3:09 AM, Hervé Le Moal
<herve....@performancevision.com> wrote:
> kern.log attached.