VTL and FC SAN sharing

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

VTL and FC SAN sharing

robyrrd
Hi,

I would try to create a VTL server (like the appliances that various vendor offer on the market) that share drives&libraries in my SAN FC with one o more FC HBA.

(the goal would be to try to use MHVTL with IBM AS400 :-))

Is it possible?

Could you help me please? ...i've read something regarding iSCSI, but for me is better to share via FC!

Regards
Roberto
Reply | Threaded
Open this post in threaded view
|

Re: VTL and FC SAN sharing

Mark Harvey
Administrator
As I understand, the SCST can be configured with Fibre-channel rather than iSCSI.

See posting :
http://mhvtl-linux-virtual-tape-library-community-forums.966029.n3.nabble.com/MHVTL-via-FC-using-SCST-Target-td1684627.html

I've not tried this as yet, but when I find some free time and HBA card, it's high on my todo list :)

Cheers
Mark
Regards from Australia
Mark Harvey
Reply | Threaded
Open this post in threaded view
|

Re: VTL and FC SAN sharing

robyrrd
Hi Mark,

where are you from?

...I could try to retrive an HBA for you :-)

R
Reply | Threaded
Open this post in threaded view
|

Re: VTL and FC SAN sharing

Mark Harvey
Administrator
Sydney, Australia :)

FWIW: I should be able to find a suitable HBA at work. It's more the 'spare time' issue that's preventing the testing.

Many thanks for the offer.
Regards from Australia
Mark Harvey
Reply | Threaded
Open this post in threaded view
|

Re: VTL and FC SAN sharing

eric
In reply to this post by robyrrd
I have SCST working with a QLogic QLA2342 card using a recent post 2.0 version of SCST. My base OS is Ubuntu 10.04 X86_64, and I am using a generic 2.6.32.27 kernel.  There are no problems exporting the virtual changers or tape drivers from MHVTL over fibre channel to  Solaris,  IRIX and Linux FC clients.  I am currently running MHVTL 0.19.  Its not hard to build the SCST package if you have experience building kernels and have added in modules.

I also use SCST to split up some 2TB drives into smaller LUNs and export them over FC, so I can test shared file systems.

In the past I used an old 32 bit system with older versions of Ubuntu, MHVTL and SCST and that also worked.

Eric
Reply | Threaded
Open this post in threaded view
|

Re: VTL and FC SAN sharing

robyrrd
Maybe, you have a guide to do this?

...a have't experience in compiling kernel, but I would try :-)

I would like to use centos o rhel for my test....

Thanks a lot
Roberto
Reply | Threaded
Open this post in threaded view
|

Re: VTL and FC SAN sharing

eric
As RHEL 5 uses an old kernel I decided not to use it, as SCST wants a recent generic kernel.  I have not tried RHEL 6 yet.  Ubuntu server is light weight, uses a recent kernel, and for a VTL, I think its a better base OS.

I have some notes for how I built SCST on Ubuntu, but they probably would not help if you are going to use RHEL, and they are not detailed enough to use by themselves to go into how to build a custom kernel or make the needed modifications to support the Qlogic card in target mode.

I would recommend downloading SCST and give it a try.

Eric
Reply | Threaded
Open this post in threaded view
|

Re: VTL and FC SAN sharing

Mark Harvey
Administrator
Hi Eric,

Would you mind posting your notes anyway ?

Testing FC is something I would like to do.

The bit I'm interested in is the 'modifications to support the Qlogic card in target mode'. Which as you have stated, is not detailed.. So any extra bits you could throw my way would be appreciated. :)

Cheers
Mark
Regards from Australia
Mark Harvey
Reply | Threaded
Open this post in threaded view
|

Re: VTL and FC SAN sharing

eric
Building SCST for MHVTL:

NOTE1: This procedure assumes you know how to build, patch and install Linux Kernels, and work around scripting issue.

NOTE2: These are my internal notes.  They may or may not help you. They are not complete and are probably wrong in more then one place.  Please double check everything you do.  Some steps can render your systems un-bootable, loose all your data, …  

NOTE3: Many of the steps below are taken from other posts, OS manuals, SCST and MHVTL documentations, and many other sources.  I do not want to take credit for other peoples work.  I am just glad its all out there, so people like me can use it.


Base Hardware and Software

The hardware used is an HP AMD disktop system that includes a AMD Athlon 64  processor,  1 GB RAM,  internal SATA drive, 1 Qlogic QLA2342 2 Gbit/sec card. The Qlogic card is a PCI-X 64 bit card plugged into a 32bit slot, leaving some of the pins hanging in the air.  This has not been an issue.

The OS used is Ubuntu 10.04 Server 64bit.  During the install, when it asks for what server software packages to install, select only ssh server.

Updating and adding needed packages: 
login
sudo -i (saves time) 
  apt-get update 
  apt-get upgrade 
  reboot after this step 
  apt-get install kernel-package 
  apt-get install open-iscsi 
  apt-get install mtx 
  apt-get install lsscsi 
  apt-get install sg3-utils 
  apt-get install openssl openssl-doc libssl-dev 
  apt-get install libncurses5-dev 
  apt-get install qla-tools
  apt-get install syslogd
  apt-get install subversion 
Build a Custom Linux Kernel

As Ubuntu 10.04 uses 2.6.32 as its base, I decided to use the generic 2.6.32.27 kernel for this system, as it the latest patched version of 2.6.32 at the time of this build.

Install the scst files so we can patch the kernel. As scst code is continually being updating, just grab the most current version and it should work.  If you want to use the exact version I tested, checkout version 3177. To check out the latest version:

   svn co https://scst.svn.sourceforge.net/svnroot/scst/trunk scst

Download linux-2.6.32.27.tar.bz2 from kernel.org, put it into /usr/src

Setup the kernel build directory:
  cd /usr/src
  tar xvjf linux-2.6.32.27.tar.bz2   
  ln -s linux-2.6.32.27 linux
  ln -s linux-2.6.32.27 linux-2.6.32

Replace Qlogic qla2xxx driver with the one from the scst package
  cd /usr/src/linux/drivers/scsi
  mv qla2xxx/ qla2xxx_orig
  ln -s /root/scst/qla2x00t/ qla2xxx
  patch the kernel with scst patches
  cd /usr/src/linux
    patch  -p1 < /root/scst/scst/kernel/scst_exec_req_fifo-2.6.32.patch
    patch  -p1 < /root/scst/iscsi-scst/kernel/patches/put_page_callback-2.6.32.patch

Setup the kernel config file
  cp /boot/config-2.6.32-21-server /usr/src/linux/.config
  cd /usr/src/linux

setup the kernel to use the Ubuntu config file and set the kernel name:
  make oldconfig
     answer yes to the questions about qla2xxx target mode
  vi Makefile and change
  EXTRAVERSION = .27  to   EXTRAVERSION = .27-FC-Target
 
  Compile and install the new 2.6.32.27 kernel
  make -j 2 bzImage
  make -j 2 modules
    NOTE: The above step takes about 2 hours on a 2 GHz system
  make modules_install && make install

Create a new initrd file
  To add the Qlogic firmware to the initrd file, so the card will work:
     Copy the  ql2300_hook script to /etc/initramfs-tools/hooks
     chmod 755 /etc/initramfs-tools/hooks/ql2300_hook

Download the Qlogic firmware from: ftp://ftp.qlogic.com/outgoing/linux/firmware/
  copy the firmware to the correct location
  cd /lib/firmware
  mkdir 2.6.32.27-FC-Target
  cp the .bin files to 2.6.32.27-FC-Target
      For the QLA2342 card I am using the Qlogic firmware version 3.03.20 IPX
 
  /usr/sbin/update-initramfs -c -k 2.6.32.27-FC-Target 
   ignore warning:
    mkdir: cannot create directory `/tmp/mkinitramfs_ehFSwq/lib/firmware': File exists existing files

Update grub
  run update-grub2
  check the /boot/grub/grub.cfg to make sure the new kernel is booted by default, otherwise edit  /etc/default/grub and change the GRUB_DEFAULT=# to match your new kernel location.  The count starts at 0.

reboot 

Build SCST for FC and iSCSI Target Support

The default build for scst is with debug turn on.  It is possible to build a non-debug version using the "make debug2release" command in each sub-system, but as this is all experimental code, it is best to run it with debugging turned on.

cd /root/scst/scst/src
vi Makefile
  Uncomment: EXTRA_CFLAGS += -DCONFIG_SCST_STRICT_SERIALIZING
  Needed for tape emulation
cd /root/scst/
make scst scst_install
make iscsi iscsi_install
make qla qla_install
make scstadm scstadm_install

Test
modprobe scst
modprobe scst_changer
modprobe scst_tape
modprobe qla2x00tgt
modprobe iscsi-scst

ls -l /sys/kernel/scst_tgt/targets/*
/sys/kernel/scst_tgt/targets/iscsi:
total 0
-rw-r--r-- 1 root root 4096 2010-12-21 21:24 mgmt
-r--r--r-- 1 root root 4096 2010-12-21 21:24 open_state
-rw-r--r-- 1 root root 4096 2010-12-21 21:24 trace_level
-r--r--r-- 1 root root 4096 2010-12-21 21:24 version

/sys/kernel/scst_tgt/targets/qla2x00t:
total 0
drwxr-xr-x 5 root root    0 2010-12-21 21:21 21:00:00:e0:8b:1d:0d:ea
drwxr-xr-x 5 root root    0 2010-12-21 21:21 21:01:00:e0:8b:3d:0d:ea
-rw-r--r-- 1 root root 4096 2010-12-21 21:21 mgmt
-rw-r--r-- 1 root root 4096 2010-12-21 21:21 trace_level
-r--r--r-- 1 root root 4096 2010-12-21 21:21 version
The above output for the qla2x00t was with a Qlogic 2342 card

Setup init scripts to auto setup exported devices and auto start everything

  Delete /etc/init.d/qla2x00t, as will do the work in /etc/init.d/scst
     rm -f /etc/init.d/qla2x00t
  Modify /etc/init.d/scst, so the SCST_MODULES line looks like:
    SCST_MODULES="scst scst_disk scst_vdisk scst_tape scst_changer qla2x00tgt"

Setup the start scripts so mhvtl starts first, then scst and finally iscsi-scst and qla2x00
   update-rc.d mhvtl start 91 2 3 4 5 . stop 9 0 1 6 .
   update-rc.d scst start 92 2 3 4 5 . stop 8 0 1 6 .
   update-rc.d iscsi-scst start 93 2 3 4 5 . stop 7 0 1 6 .
NOTE: Warning about missing LSB information or runlevel arguments can be ignored


Create the /etc/scst.conf file

  Use lsscsi to list the devices
    #lsscsi

  [0:0:0:0]    disk    ATA      ST3402112AS      3.BH  /dev/sda
  [8:0:0:0]    mediumx QUANTUM  PX500            001A  /dev/sch0
  [8:0:1:0]    tape    IBM      ULTRIUM-TD4      85V1  /dev/st0
  [8:0:2:0]    tape    IBM      ULTRIUM-TD4      85V1  /dev/st1
  [8:0:3:0]    tape    IBM      ULTRIUM-TD4      85V1  /dev/st2
  [8:0:4:0]    tape    IBM      ULTRIUM-TD4      85V1  /dev/st3


Then create a /etc/scst.conf file to create all the targets. Base on the above  info:
# Header Info
setup_id 0x11
threads 4
# Changer Devices 
HANDLER dev_changer {
    DEVICE 8:0:0:0
}
# Tape Devices 
HANDLER dev_tape {
    DEVICE 8:0:1:0
    DEVICE 8:0:2:0
    DEVICE 8:0:3:0
    DEVICE 8:0:4:0
}

# Qlogic Devices 
TARGET_DRIVER qla2x00t { 
    TARGET 21:00:00:e0:8b:1d:0d:ea {
            LUN 0 8:0:0:0
            LUN 1 8:0:1:0
            LUN 2 8:0:2:0
            LUN 3 8:0:3:0
            LUN 4 8:0:4:0
            enabled 1
     }
     TARGET 21:01:00:e0:8b:3d:0d:ea {
            LUN 0 8:0:0:0
            LUN 1 8:0:1:0
            LUN 2 8:0:2:0
            LUN 3 8:0:3:0
            LUN 4 8:0:4:0
            enabled 1
     }
}

# ISCSI Devices 
TARGET_DRIVER iscsi {
      enabled 1
      TARGET iqn.2010-12.zzz.vtl3 { 
           LUN 0 8:0:0:0
           LUN 1 8:0:1:0
           LUN 2 8:0:2:0
           LUN 3 8:0:3:0
           LUN 4 8:0:4:0
           enabled 1
     }

} 
reboot

/etc/initramfs-tools/hooks/ql2300_hook file, based on http://vovo2000.com/phpbb2/viewtopic-337519.html

#!/bin/sh -e
# initramfs hook for ql2xxx firmware loading
PREREQ="udev"
# Output pre-requisites
prereqs()
{
  echo "$PREREQ"
}

case "$1" in
    prereqs)
    prereqs
    exit 0

   ;;

esac

. /usr/share/initramfs-tools/hook-functions
mkdir ${DESTDIR}/lib/firmware
cp -p /lib/firmware/ql2300_fw.bin ${DESTDIR}/lib/firmware/
cp -p /lib/udev/firmware.sh ${DESTDIR}/lib/udev/
cp -p /lib/udev/rules.d/50-firmware.rules ${DESTDIR}/lib/udev/rules.d
nia
Reply | Threaded
Open this post in threaded view
|

Re: VTL and FC SAN sharing

nia
Administrator
fyi, I have tried the EMULEX scst driver http://lpfcxxxx.sourceforge.net/HOWTO.lpfc 
with a couple of 2G LP9002 HBAs, but found out at end that only newer 4G LP11xxx and up HBAs are supported by the scst emulex driver.

This was not clearly documented:

 <quote author="James Smart <james.smart@em...> -2011-02-15 01:25">
Re: [Scst-devel] Emulex HBA in target mode : "Error inserting lpfc_scst" + "Unable to init target sliport":

The lpfc adapters have 2 versions of f/w interface - what we call SLI-2 and
SLI-3.  Both versions are contained in the f/w image supported on LP11xxxx and
up adapters, while only SLI-2 is in the f/w images for LP9xxx and LP10xxxx
(and lower) adapters.

Unfortunately, although SLI-2 does have target mode support, the SCST driver
is only functional with SLI-3.  In order for SCST to run, you will need to
have a newer adapter (4G or better, which corresponds to LP11xxx and up)..

-- james s
nia
Reply | Threaded
Open this post in threaded view
|

Re: VTL and FC SAN sharing

nia
Administrator
This post was updated on .
In reply to this post by eric
I was able to buy a couple of working Qlogic HBA's dual ports 2342 from ebay for $15 each  so I have tried this also.

I followed Eric's notes (Very Helpful) along with instructions posted on scst web site http://scst.sourceforge.net/qla2x00t-howto.html.

I did not have to implement the initramfs ql2300 hook. Did not need it.

I am using a 32-bit system, Intel 2Ghz with 1.5G RAM. I used a generic kernel also 2.6.33.7 with Oracle Linux 5.6 using same kernel config--2.6.18-238.el5. I had many lock-up troubles with scst after the compile due to using latest svn at the time (3394), but after retrying with same what Eric posted (3171), everything was fine. Since, I was running a 32-bit platform, I had to turn OFF HIGHMEM and use VMSPLIT 2/2 as recommended by the scst for performance reasons.

I was able to export changers and drives to a 64-bit Solaris 11 express system without any issues and use networker & TSM to test along with IBM Tape drivers in Solaris.
Everthing is behaving normal except some performance issue that I cannot determin the cause yet if any .. I am getting about 3-10 MB/S .. It could be the Target host that is the bottle Neck .. Not sure yet. But I am happy to see my Solaris System connected to tape :-) .. My previous iscsi attempt setup for Solaris had issues with my backup application but now with FC, all running fine.

nia
Reply | Threaded
Open this post in threaded view
|

Re: VTL and FC SAN sharing

Eric Engberg
Building custom CentOS 6.4 kernel

Thanks go to Eric for his previous post on building a kernel for Ubuntu as without it I would not have been able to do this most likely.  I also skipped the step of adding qlogic firmware and hook to the initrd that nia skipped.  Seems that wasn't needed here either.  For my purposes I was only interested in communcation over Fibre Channel so you are on your own for any additional steps that may be needed for using iSCSI if you need it.  I was able to successfully create targets for all my mhvtl devices and see them on a Windows machine across fibre channel.

Install required packages
sudo yum install "Development Tools"
sudo yum install mtx lsscsi subversion openssl ncurses-devel hmaccalc zlib-devel binutils-devel elfutils-libelf-devel rpm-build redhat-rpm-config asciidoc ExtUtils-Embed xmlto binutils-devel newt-devel python-devel zlib-devel

Checkout SCST
svn co https://scst.svn.sourceforge.net/svnroot/scst/trunk ~/scst

Download and 'install' kernel SRPM
rpm -ivh http://vault.centos.org/6.4/updates/Source/SPackages/kernel-2.6.32-358.11.1.el6.src.rpm 2>&1 | grep -v mock
  This is the current kernel for RHEL/CentOS 6.4 at the time of this post.  You may want to grab the correct rpm for the kernel you are currently running if you are on a different version.
 
Setup RPM build
cd ~/rpmbuild/SPECS
sudo rngd -r /dev/urandom
rpmbuild -bp --target=$(uname -m) kernel.spec

Replace qla2xxx driver with driver from scst (these steps may be able to be skipped as we'll end up blacklisting qla2xxx later on)
cd ~/rpmbuild/BUILD/kernel-2.6.32-358.11.1.el6/linux-2.6.32-358.11.1.el6.`uname -m`/drivers/scsi/
mv qla2xxx qla2xxx_orig
ln -s ~/scst/qla2x00t qla2xxx

Copy config
cd ~/rpmbuild/BUILD/kernel-2.6.32-358.11.1.el6/linux-2.6.32-358.11.1.el6.`uname -m`
cp configs/* ~/rpmbuild/SOURCES
cp configs/kernel-2.6.32-`uname -m`.config .config

Apply patches to kernel
patch -p1 < ~/scst/scst/kernel/scst_exec_req_fifo-2.6.32.patch
patch -p1 < ~/scst/iscsi-scst/kernel/patches/rhel/put_page_callback-2.6.32-279.patch
  This patch is for 2.6.32-279 but seemed to apply without issue.
 
Fix compile error in blk-map.c 
perl -pi -e 's/int res;$/int res = -EINVAL;/ if $. == 397;' block/blk-map.c
  This changes line 397 from 'int res;' to 'int res = -EINVAL;'.  Kernel will fail to compile without this change.

Create kernel config
make oldconfig
  answer yes to the questions about qla2xxx target mode
 
perl -pi -e 's/^EXTRAVERSION .*/EXTRAVERSION = -358-FC-Target/' Makefile

make menuconfig
  This step can be skipped if you don't plan to change any config options
 
cp .config configs/kernel-2.6.32-`uname -m`.config
cp configs/* ~/rpmbuild/SOURCES
 
Build and install RPM
make -j 2 rpm
sudo yum install ~/rpmbuild/RPMS/`uname -m`/kernel-2.6.32358FCTarget-1.`uname -m`.rpm


You'll also need to update your /boot/grub/grub.conf to configure the new kernel for use.  Here are the lines I used but these may not work for you.

title CentOS (2.6.32-358-FC-Target.el6.x86_64)
        root (hd0,0)
        kernel /vmlinuz-2.6.32-358-FC-Target ro root=/dev/mapper/vg_nbqamedia-lv_root nomodeset rd_NO_LUKS  KEYBOARDTYPE=pc KEYTABLE=us LANG=en_US.UTF-8 rd_NO_MD rd_LVM_LV=vg_nbqamedia/lv_root SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=vg_nbqamedia/lv_swap rd_NO_DM rhgb quiet
        initrd /initramfs-2.6.32-358-FC-Target.img
       
Additionally if you already had mhvtl installed you will need to rebuild and reinstall the kernel module for it to work again.

Building and configuring SCST
Originally I wasn't going to write this section and just point anyone following this guide to Eric's section above but there were some changed and new steps I had to complete for this.  Most of it is unchanged though.

vi ~/scst/scst/src/Makefile
  Uncomment: EXTRA_CFLAGS += -DCONFIG_SCST_STRICT_SERIALIZING
  Needed for tape emulation

Remove and blacklist existing qla2xxx module in preparation for new scst based module
rmmod qla2xxx
echo blacklist qla2xxx >/etc/modprobe.d/blacklist-qla2xxx.conf

Enable dual mode for fibre card
echo “options qla2xxx_scst qlini_mode=enabled” > /etc/modprobe.d/qla2xxx_scst.conf
  (Optional) Enables dual mode so that the card can be in both initiator and target mode.  I required this feature as I needed to also mount a LUN from another storage unit. This seemed to work ok for me but some of the material I referenced online mentions that some switches may not support this mode.

Build SCST 
make scst
sudo make scst_install
make qla
sudo make qla_install
make scstadm
sudo make scst_install

Test loading SCST modules
modprobe qla2xxx_scst
modprobe scst
modprobe scst_changer
modprobe scst_tape
modprobe scst_disk
modprobe scst_vdisk
modprobe qla2x00tgt

Change init script
sudo perl -pi -e 's/^\s+SCST_MODULES="scst"$/SCST_MODULES="scst scst_disk scst_vdisk scst_tape scst_changer qla2x00tgt"/' /etc/init.d/scst
  Changes the line with SCST_MODULES="scst" to SCST_MODULES="scst scst_disk scst_vdisk scst_tape scst_changer qla2x00tgt"
sudo perl -pi -e 's/^#\s* chkconfig: .*/# chkconfig:      2345 31 31/' scst
  Changes the chkconfig init priority of SCST to be 31 so it starts after mhvtl which defaults to a priority of 30.  These values work ok for me but you may need to adjust for your environment.

Create SCST config file
Since every environment is likely to be fairly or even vastly different than one another I thought rather than paste my config, give you a generic example, or try to explain the config myself I thought I'd just point you in the direction of documentation and other reference material.
I really only came across 3 sources that I pulled from when writing my config I believe.  Eric's post above, the man page for scst.conf, and https://git.ipxe.org/mirror/scst/.git/blob_plain?f=scstadmin/README

Test SCST config
You should test your SCST config by starting it from the command line the first time.  I didn't do this at first and ended up chasing a problem that didn't exist and was just a small config mistake.

scstadmin -config /etc/scst.conf

At this point if you enabled dual initator/target mode you can cat out /sys/module/qla2xxx_scst/parameters/qlini_mode and it should say 'enabled'.  If it still says 'exclusive' then dual mode has not been enabled.
To see what mode your card is currently in you can cat out /sys/class/scsi_host/host#/active_mode replacing # with the correct number for your HBA card/port.  It should say "Initiator, Target", Target, or just Initiator if you haven't enabled a target or scst has been improperly configured.

Make new initramfs and reboot
sudo mkinitrd /boot/initramfs-2.6.32-358-FC-Target.img 2.6.32-358-FC-Target
reboot

After the machine has rebooted you should check to make sure everything has come up properly.

Initially after I had completed all the steps I was unable to see my devices across on the remote machine and wasn't able to figure out why.  I had thought that I either got something wrong when building SCST or the custom kernel or possibly needed to update the firmware on my QLA2342 cards (which incidently I still haven't figured out how to do.  Finding a way to boot into DOS AND be able to read a usb stick or disk with the required executable/firwmare on an IBM x336 has proven difficult to say the least).  It turns out I simply had the 'enabled' option in the wrong place in my config.

Some useful tips I can provide on troubleshooting issues are to manually start SCST and not from the init script.  When I started it using 'scstadmin -config /etc/scst.conf' I saw my problem pretty clearly.
Also the /sys file system in linux can be very useful in poking around into how the card is currently configured and what is going on with it.  On my system since the QLA2342 has 2 ports on it there were 2 entries under /sys/class/scsi_host for the card which were host2 and host3.  The files within the host directories are driver dependant I think and will probably be different for different cards.

Useful files for my QLA2342 under '/sys/class/scsi_host/host3/' on my system were active_mode, model_name, and supported_mode.  You can cat any of these files to find out special info about the card.
The active_mode file says what the current mode of the card is: Initiator, Target or 'Initiator, Target' for dual mode.  This will be Initiator unless you've successfully configured a target on the port with SCST and enabled it.  This file is what helped me figure out that the card was not in target mode because I had the 'enabled' option in the wrong location in the config.
The model_name file contains the model of the card. Mine said QLA2352 but I'm pretty sure the cards I bought were 2342 and I found no mention of a QLA2352 online really.
The supported_mode file lists the modes the card/driver are capable of.  The normal driver and kernel will only contain Initiator.  If you've built the new kernel correctly it should say "Initiator, Target".


Here is a list of links for everything I used for reference while creating this guide:
Building custom RHEL kernel
Getting RHEL kernel
Fix for block/blk-map.c
Forum post pointing out RHEL specific patches for SCST.  Thanks mvrk for posting your own follow-up solution
Good scst.conf documentation and examples
Guide for building SCST for QLogic cards.  The step to blacklist the qla2xxx module came from here
Step to enable dual target/initiator mode came from here
nia
Reply | Threaded
Open this post in threaded view
|

Re: VTL and FC SAN sharing

nia
Administrator
Nice to see any updated write up on this

Thank you !

-nia