Openfiler 2.99 fiber channel setup

Submitted by Tom L'Ecluse on Sun, 19/06/2011 - 12:49

OpenfilerFor openfiler 2.3 I found a guide on the forums: https://forums.openfiler.com/viewtopic.php?id=3422

Which worked flawlessly. With openfiler 2.99 the scstadmin package has been updated to version 2 instead of version 1. With this update the syntax has been changed.

So this is my reworked version of Snick his tutorial.

 

This tutorial is to use on your own risk. I use this with a qla 2460 and qla 2462 card. If you have another card then you should load some other driver or service.

1. Install openfiler without your fiber card in the system.

You can use the standard tutorial for this: http://www.openfiler.com/learn/how-to/graphical-installation but make sure that your fiber card isn't in your system!!!

2. Update openfiler

Update openfiler after the installation. I use the ssh command "conary updateall" to follow the process instead of the gui. But the gui works also! Use what you prefer.

3. Reboot after updates.

Reboot & go to step 2 until no updates are available or installable.

4. Shutdown and add fiber card.

Shutdown openfiler and install your fiber card.

5. Boot openfiler with fiber card.

Boot openfiler while the fiber card is in the system.

6. Edit the /etc/init.dscst file to fix some problems.

Edit the /etc/init.d/scst file with a text editor and search for comment that reads:

chkconfig - 14 87

and replace it with the line:

chkconfig - 99 36

I don't know if this is still required but I use it. Test it yourself if necessiary.

7. Enable the services

Next step is to enable the scst & qla2x00tgt service by executing the following:

chkconfig scst on
chkconfig qla2x00tgt on

I will use qla2x00t as Y in the next commands.
Note that the last command is to load a Qlogic target driver. If you use a different card then you should load up another module or service. Use the openfiler forums or google.

8. Find WWN of your openfiler fiber cards.

Find your WWN from your openfilers fiber card using the command:

cat /sys/class/fc_host/host*/port_name


And write them down. I will use them as X in the following commands. If you have more than 1 fiber channel, like me (QLA 2462) card then you must use the same command multiple times with a different WWN.

9. Start the services

Start the scst service by executing:

service qla2x00tgt start
service scst start

Don't mind the errors. This is due to the fact that the config file isn't ok.

10. Enable target mode

Enable target mode for each adapter or interface you want to use for target service with the following command (where X is the WWN seperated by colons for example "21:01:00:1b:32:13bd:32":

scstadmin -enable_target X -driver Y

In my case it was:

scstadmin -enable_target 21:01:00:1b:32:13bd:32 -driver qla2x00t

11. Create a security group.

Create a security group for the devices that will be using your target. For example, I will name my security group esxi because my esxi servers will be connecting to openfiler for their datastores. The groupname will be used as Z in the next commands. Use the command:

scstadmin -add_group Z -driver Y -target X

In my case it was:

scstadmin -add_group esxi -driver qla2x00t -target 21:01:00:1b:32:13bd:32

12. Assign servers to the security group.

Assign servers to the security group. You need to find the wwn of every server that you want to connect to the openfiler server using fiber channel (Will use these WWN as W). On Esxi you can easily find this by going to Configuration > Storage Adapters and then selecting the storage adapter where you want the WWN from. See screenshot bellow.

with the following command:

scstadmin -add_init W -driver y -target x -group Z

In my case it was:

scstadmin -add_init 50:01:43:80:03:bc:3a:9d -driver qla2x00t -target 21:01:00:1b:32:13bd:32 -group esxi
scstadmin -add_init 50:01:43:80:03:bc:3a:9c -driver qla2x00t -target 21:01:00:1b:32:13bd:32 -group esxi

13. Create logical volume.

Next create a logical volume using the gui from openfiler and select iscsi / fiber channel as filesystem. I've created a volume named vol_ssd in the volume groud vg_ssd.

14. Create scst device.

Now it's time to create a fiber channel device that points at this logical volume. Use the following command replace V with a label that you assign and U with the full path to the logical volume created in the previous step. T is how you will be accessing your storage. You can see all the options by doing the command:

scstadmin -list_handler

Then run the following command to create the device:

scstadmin -open_dev V -handler T -attributes filename=U

In my case:

scstadmin -open_dev vol_ssd -handler vdisk_fileio -attributes filename=/dev/vg_ssd/vol_ssd

15. Assign virtual disk to security group and lun.

Now it's time to assign the virtual disk to a security group. Use the following command where S is the LUN number starting with 0. 0 Is required before any other! Use the following command:

scstadmin -add_lun S -driver Y -target W -group Z -device V

In my case:

scstadmin -add_lun 0 -driver qla2x00t -target 21:01:00:1b:32:13bd:32 -group esxi -device vol_ssd

16. Save the scst configuration.

This completes the configuration on the openfiler system. In order for this configuration to persist across rebots, enter the following command:

scstadmin -write_config /etc/scst.conf

Make sure that this command is runned each time that a change is made to the openfiler system relating to the fiber channel sub system.

17. Wrap up.

I use Point to point fiber channel connections for my server so no switch is involved. If you have a switch then you should add the necessairy zones but I recommend to use p2p first and add the switch in the mix is p2p works flawlessly. It is easier to debug without the switch.

read only

Hi, have managed to get this working however after a months operation it appears my volume has gone into a read only mode. Any ideas?

#scstadmin -list_device vol_ssd

Collecting current configuration: done.

Attribute Value Writable KEY
--------------------------------------------------------
usn 8de6b769 Yes Yes
t10_dev_id vol_ssd 8de6b769 Yes Yes
filename /dev/vg_ssd/vol_ssd No Yes

All done.

What vmware version do you

What vmware version do you use?

What vmware version do you

Using VMWare ESXi 5.1, presenting the LUN directly to a VM as a RDM and windows is reporting it as a read only. I assume its read only from the openfiler box.

Ignore my other post... I got

Ignore my other post... I got confused. Have you tried re-installing and re-adding the VM with the RDM device? There is probably a reservation in the OS configuration that was never removed properly or possibly a snapshot that has been orphaned. Re-presenting the RDM on a "fresh" host should fix this.

Never tried RDM so I can't

Never tried RDM so I can't really help there...

I used 5.1, the dell certified build for Poweredge T620

It's nice for storage vmotion.. I have two hosts running the virtual SAN and have them replicate to eachother. The current setup has a qle2462 (passthrough) and qle2462 (Native vmware) on each host. Host A port 1 plugs into VMSAN B port 2 and host A port 2 plugs into VMSAN A port 1, vice versa for Host B. With 2 x T620's, you can actually run a SAN-less environment with all the benefits of SAN storage. I reserved the bottom 4 harddrive (3.5") slots for SAN storage.

Issues

I am having two issues

1. no file created which is marked by Asterisk*

sys/class/*fc_host/hostX/port_name*

2.

#chkconfig scst on
service scst does not support chkconfig

I am using a UCS C250 server with Qlogic QLE2462 4 Gbps 2 port FC HBA

# lspci
0b:00.0 Fibre Channel: Qlogic Corp. ISP2432-based 4GB Fibre Channel to PCI Express HBA (rev 03)
0b:00.1 Fibre Channel: Qlogic Corp. ISP2432-based 4GB Fibre Channel to PCI Express HBA (rev 03)

#lsmod | egrep -i "qlo|ql|isp"
isp_mod 222280 0
isp_scst 31976 1 isp_mod
scst 168840 2 scst_vdisk , isp_scst
scsi_mod 168024 15 isp_mod,scst ,,,,,,snip..snip

I have followed the doc am unable to get this working

Install with card inside

It sounds like you're not installing the OS with the card installed, you have a bad card, or the PCI-e/PCI-X port is bad or shut off in bios.

The OS has to detect and install the card. The file you reference is created by linux and is used for diagnostic/configuration purpose. If it's missing, the device has not been installed.

Reseat and reset the cards BIOS. Upgrade BIOS on mobo and card. Check and determine if something is disabling the PCI bus during boot.

VM configuration

I've created a VM which supports PCI-e passthrough for VMWare 5.x. Does anyone know if their is any licensing between openfiler, rpath, scst, etc... that would prohibit me from making this available to the public? All it would require is changing the WWN.

Help please

Hi all,
Like others before me I've almost go it. this doesn't look right but I don't know how to fix it. I'm a Windows Guy so be kind.

[root@SAN-1 ~]# scstadmin -list_group

Collecting current configuration: done.

Driver: qla2x00t
Target: 21:00:00:1b:32:17:6c:39

Driver/target 'qla2x00t/21:00:00:1b:32:17:6c:39' has no associated LUNs.

All done.

* * * * * contents of /etc/scst.conf file * * * * *

# Automatically generated by SCST Configurator v2.0.0.

HANDLER vdisk_fileio {
DEVICE vol_ssd {
t10_dev_id "vol_ssd 8de6b769"
usn 8de6b769

filename /dev/vg_ssd/vol_ssd
}
}

TARGET_DRIVER qla2x00t {
TARGET 21:00:00:1b:32:17:6c:39 {
rel_tgt_id 1
enabled 1

GROUP SAN1 {
LUN 0 vol_ssd

INITIATOR 20:00:00:1B:32:8A:82:CE
}
}
TARGET 21:00:00:1b:32:17:6c:39{
enabled 1
}

}

Seems like you didn't associated a lun.

Did you do step 15?

I thought I did. Here's my list of commands entered.

chkconfig scst on
chkconfig qla2x00tgt on
service qla2x00tgt start
service scst start

Enable Target Mode:
scstadmin -enable_target 21:00:00:1b:32:17:6c:39 -driver qla2x00t

Create Security Group:
scstadmin -add_group esxi -driver qla2x00t -target 21:00:00:1b:32:17:6c:39

Assign Server to Security Group:
scstadmin -add_init 20-01-00-1B-32-AA-82-CE -driver qla2x00t -target 21:00:00:1b:32:17:6c:39 -group esxi

modprobe scst_disk
modprobe scst_vdisk
modprobe qla2x00tgt
modprobe scst_vdisk
modprobe scst_user
modprobe scst_modisk
modprobe scst_processor
modprobe scst_raid
modprobe scst_tape
modprobe scst_cdrom
modprobe scst_changer
modprobe ib_srpt
modprobe iscsi_scst
scstadmin -open_dev vol_ssd -handler vdisk_blockio -attributes filename=/dev/vg_ssd/vol_ssd (I'm not sure which here blockio or fileio I thought for FC or iSCSI we want blockio?)

scstadmin -add_lun 0 -driver qla2x00t -target 20:00:00:1B:32:8A:82:CE -group esxi -device vol_ssd

scstadmin -write_config /etc/scst.conf
/etc/init.d/scst restart
scstadmin -issue_lip

You don't get any errors on

You don't get any errors on the command?

Your volume has the same name as myn? /dev/vg_ssd/vol_ssd 

Is openfiler up 2 date?

Started from scratch and keeping a step by step log.

I decided to start over and I made a backup of a virgin system. In case I have to start again.

As to not fill up your blog with a long list here's a site I put up with every step I've taken so far and the results.

http://rkirchhof.com/Completelogofsetup.htm

I end with a question (Really 4 questions but the last ones most important) that's why I didn't go to the next steps. Please review and share your thoughts. When were finished you can copy the final result and post them. I intend to keep it online indefinitely. My email address is: Robert@RKirchhof.com

What to do next.

I would try to use the fileio like I did in the tutorial. I haven't got a live openfiler to test things on so.

The conary errors happens sometimes. But what I found strange was the fact that you needed to create the init scripts. The firmware shouldn't be done all the time but 1 time should be enough. So far it all looks good. Continue after these commands because if you shutdown you loose the progress or you need to save the scst.conf.

FC Setup

I'm going to pick this back up this weekend, I have some different hardware coming. MOBO I'm using has a habit of spontaneously shutting off without any apparent reason.

Do you think it's possible to get this working with maybe Ubuntu? I found instruction for installing SCST on it.

Ubuntu

You can do it on ubuntu. I've written a guide for it too. But then it is all with the shell, no gui.

FATAL: Module ub_srpt not found

Getting the error:

FATAL: Module ub_srpt not found

when entering the modprobe ub_srpt

Any idea what could be causing the error and how to fix it?

Know the problem

Hi,

the problem is that modules are hardware dependant. Some need those modules, some need others.

Thanks!!

Thank you for the response..In essence with your tutorial, setting Openfiler with FC was ok. I ended setting up two luns.

[code]
scstadmin -add_lun 0 -driver qla2x00t -target 21:00:00:1b:32:0f:1c:12 -group win7 -device movies
24a) scstadmin -add_lun 1 -driver qla2x00t -target 21:00:00:1b:32:0f:1c:12 -group win7 -device tvshows
[/code]

My problem lies elsewhere. My Windows 7 (DAS) running sansurfer is able to see the SAN, but not the LUNS I created.

With you're experience, do you have any idea where I should look to fix it ?

 photo san_zpse6859083.png

 photo san2_zps4e74b327.png

Disregard

Seems like a long (overnight) cold boot did the trick. I can see the lun and created folders on them thanks!!

FINALLY WORKING!!!

I used a Dell R710 and 2 qla2460 cards in conjunction with ESXi free 5.1 (DELL's Version). Notes and Step by Step procedure listed below!

PS. I had to update the Server completely using the Dell respository manager and creating a bootable linux ISO. This is imperative for the First Gen R710 (figured I'd save atleast someone the headache I've been through) BIOS shows version 6.3

----------------------

NOTES:

After Step 1, use WINSCP and copy qla2x00tgt to your desktop before you update!! Important as updates seem to delete driver service.

SKIP step 6

Before Step 7, copy qla2x00tgt back into /etc/init.d/
run chmod +x qla2x00tgt (to make it executable)

Step 13 didn't go as planned.... I had a previous partition on the Volume I wanted to use (MSDOS instead of GPT)
Followed this article under the section
"Clearing partitioning information in ESXi using the DD utility":

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd...

Step 15, I'm pretty sure where the target is followed by the OP's "W", is actually supposed to be "X" OPENFILER WWN, not your esxi (or whatever initiator you're using)

In between steps 13 and 14, run the following:

modprobe scst_disk
modprobe scst_vdisk
modprobe qla2x00tgt
modprobe scst_vdisk
modprobe scst_user
modprobe scst_modisk
modprobe scst_processor
modprobe scst_raid
modprobe scst_tape
modprobe scst_cdrom
modprobe scst_changer
modprobe ub_srpt
modprobe ib_srpt
modprobe iscsi_scst

This will populate your list handlers for step 14. Otherwise, you WILL get an error.

---------------------------------

PROCEDURE:

1) Install openfiler 2.99.1 without your fibre card
2) WINSCP in and copy out /etc/init.d/qla2x00tgt
3) conary update conary
4) conary updateall
5) REBOOT
6) Wait for system to completely load.
7) SHUTDOWN
8) Install Fibre card
9) Boot up
10) WINSCP in and copy in /etc/init.d/qla2x00tgt that you copied off
11) chmod +x /etc/init.d/qla2x00tgt
12) chkconfig scst on
13) chkconfig qla2x00tgt on
14) cat /sys/class/fc_host/host*/port_name
(write down this wwn, it will be [OPENFILERWWN])
15) service qla2x00tgt start
16) service scst start
17) scstadmin -enable_target [OPENFILERWWN] -driver qla2x00t
18) scstadmin -add_group esxi -driver qla2x00t -target [OPENFILERWWN]

Before step 19, log into vsphere and write down the WWN under storage adapters, ISP2432-based 4Gb Channel to PCI Express HBA. It's the second half of the number, beginning with 21:. That will be [ESXWWN]

19) scstadmin -add_init [ESXWWN] -driver qla2x00t -target [OPENFILERWWN] -group esxi

20) If your Physical disk isn't a GPT partition, you will need to follow the article below, otherwise, create a volume named vol_ssd and volume group named vg_ssd and jump to step 21. Make sure volume is Block (ISCSI, FC, etc)

Followed this article under the section
"Clearing partitioning information in ESXi using the DD utility":

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd...

21) Run the following modprobe commands to populate your list handlers. Do this one by one:
modprobe scst_disk
modprobe scst_vdisk
modprobe qla2x00tgt
modprobe scst_vdisk
modprobe scst_user
modprobe scst_modisk
modprobe scst_processor
modprobe scst_raid
modprobe scst_tape
modprobe scst_cdrom
modprobe scst_changer
modprobe ub_srpt
modprobe ib_srpt
modprobe iscsi_scst

22) scstadmin -list_handler
(You should see 'vdisk_fileio' listed as a handler

23) scstadmin -open_dev vol_ssd -handler vdisk_fileio -attributes filename=/dev/vg_ssd/vol_ssd
24) scstadmin -add_lun 0 -driver qla2x00t -target [OPENFILERWWN] -group esxi -device vol_ssd
25) scstadmin -write_config /etc/scst.conf

Literally from there, I was able to plug in my cable and see the LUN on ESXi.

Thanks for this article. You've saved me a ton of money.
-Chris

handlers

Hi,

Running the modprobe commands you mention works fine until I reboot?
Could somebody help me out please?

Thanks.

For kicks

Are you getting an error? The more info the better...

Run the following two commands if your LUNS are presented, but everything else is working:

/etc/init.d/scst restart

scstadmin -issue_lip

typo

*aren't not are

Glad it worked out! Thanks

Glad it worked out! Thanks for posting some solutions for other users.

Trouble again...

It seems that this configuration only lasts for one reboot. After which, the LUN is no longer presented to ESX. I've re-run all steps, the openfiler GUI shows a LUN available on the qla2460, but esx fails to recognize it. Back to the drawing board....

LOL.... Nevermind.

Restarting SCST wasn't re-presenting the LUN. Further investigation of the indicator lights on the QLA cards showed a flashing pattern. Disconnecting the cable and re connecting it seems to resolve the issue. I can only assume that's why I got such a bargain deal on these card off of ebay. Anyway, all is well.

Try updating the firmware.

Try updating the firmware. There was some problems with them before the latest firmware!

Fixed the problem

scstadmin -issue_lip

Put this command in my rc.local and any time I restart the scst service.

Just check if the

Just check if the /etc/scst.conf has your configuration saved.
Then check if the necessairy services are started.

No Handler

Hi,

First of all, thx for making a how-to. It would have been nice if it worked straight after installing but ok, maybe next year. :)

I'm using some SSD drives on a LSI 9265-8i and a Qlogic 2460 fiber card.

I've managed to get to step 14 without too many problems, but i don't seem to have any handlers?? scstadmin -list_handler

[root@openfiler ~]# scstadmin -list_handler

Collecting current configuration: done.

Handler

All done.

[root@openfiler ~]# scstadmin -open_dev vol_ssd -handler vdisk_fileio -attributes filename=/dev/vg_ssd/vol_ssd

Collecting current configuration: done.

-> Making requested changes.
-> Opening device 'vol_ssd' using handler 'vdisk_fileio': done.

FATAL: Received the following error:

No such handler exists.

[root@openfiler ~]#

Any ideas?

There's nothing about the handlers in the /etc/scst.conf file either.

Thx

LUN's not masking? Is my scst.conf correct?

Not sure if my LUN’s are masking to hosts. Have two LUN’s 0 and 1. Each I believe is masked to all of my initiators:

INITIATOR 20:00:00:25:B5:10:B8:1F
INITIATOR 20:00:00:25:B5:10:A8:1F
INITIATOR 20:00:00:25:B5:10:A8:0F
INITIATOR 20:00:00:25:B5:10:B8:0F

Each host is dual homed. Even though zoning only allows each host HBA to see one target on the openfiler, I masked all anyhow. Kind of in debug stage here.
Is my configuration missing the actual masking? I seem my servers are not seeing the LUN’s. I know the SAN Zoning etc, is fine.

At SCST Configurator v2.0.0

cat /etc/scst.conf

# Automatically generated by SCST Configurator v2.0.0.

HANDLER vdisk_blockio {
DEVICE craigsfcvolume {
t10_dev_id "craigsfcvolume c27d97b3"
usn c27d97b3

filename /dev/dasvolume/craigsfcvolume
}

DEVICE v-crsimp01 {
t10_dev_id "v-crsimp01 e951d814"
usn e951d814

filename /dev/dasvolume/v-crsimp01
}
}

TARGET_DRIVER qla2x00t {
TARGET 21:00:00:1b:32:01:2b:04 {
rel_tgt_id 2
enabled 1

GROUP DASBOOT {
LUN 0 craigsfcvolume
LUN 1 v-crsimp01

INITIATOR 20:00:00:25:B5:10:B8:1F

INITIATOR 20:00:00:25:B5:10:A8:1F

INITIATOR 20:00:00:25:B5:10:A8:0F

INITIATOR 20:00:00:25:B5:10:B8:0F
}
}

TARGET 21:01:00:1b:32:21:2b:04 {
rel_tgt_id 1
enabled 1

GROUP DASBOOT {
LUN 0 craigsfcvolume
LUN 1 v-crsimp01

INITIATOR 20:00:00:25:B5:10:B8:1F

INITIATOR 20:00:00:25:B5:10:A8:1F

INITIATOR 20:00:00:25:B5:10:A8:0F

INITIATOR 20:00:00:25:B5:10:B8:0F
}
}
}

With one server booted I see

With one server booted I see the WWPN's logged in at filer

Collecting current configuration: done.

Driver/Target: qla2x00t/21:00:00:1b:32:01:2b:04

Session: 20:00:00:25:b5:10:a8:0f

Attribute Value Writable KEY
-----------------------------------------------------------------
active_commands 0 Yes No
commands 0 Yes No
initiator_name 20:00:00:25:b5:10:a8:0f Yes No

Session: 21:fd:00:05:1e:90:17:0c

Attribute Value Writable KEY
-----------------------------------------------------------------
active_commands 0 Yes No
commands 0 Yes No
initiator_name 21:fd:00:05:1e:90:17:0c Yes No

Driver/Target: qla2x00t/21:01:00:1b:32:21:2b:04

Session: 20:00:00:25:b5:10:b8:0f

Attribute Value Writable KEY
-----------------------------------------------------------------
active_commands 0 Yes No
commands 0 Yes No
initiator_name 20:00:00:25:b5:10:b8:0f Yes No

Session: 21:fd:00:05:1e:90:17:0c

Attribute Value Writable KEY
-----------------------------------------------------------------
active_commands 0 Yes No
commands 0 Yes No
initiator_name 21:fd:00:05:1e:90:17:0c Yes No

All done.

Can someone explain what it is ...

that makes it critical to *do the install while the FC card is not in the machine*?

It may not be obvious, but this means that *you can't add FC to a running filer*; that seems... poorly planned, at best. If we at least knew *precisely what step* needs to not see the card, that would help a lot in circumstances where people want to add FC capability to an already installed filer.

In my particular case, my filer isn't in production yet, so I can afford to reinstall it. But I'm sure the other case isn't especially uncommon....

Can you, Snick, or rafiu speak to precisely what we're trying to avoid there?

target driver not available

thanks a lot for this. this is really helpful. however, i always get the following error

targetAttributes(): Driver 'qla2x00tgt' is not available

any advice?

thanks
robert

target driver not available

thanks a lot, that worked.

Load the service for the driver.

Yeah you should do this:

service qla2x00tgt start

or

/etc/init.d/qla2x00tgt start

Updated the guide.

Hello. First of all, thanks

Hello. First of all, thanks for posting this info.. I think I am very close but not quite there.. I am very weak on my Linux skills so plz forgive me if this is something very simple.

#1. I had already installed the new OF on to my server with the QL fiber card installed. Seems to be using the same driver you are working with.

#2. went through all the steps and have added the group and the lun to the FC target.. here is what my FC-Target screen reads from the OF GUI.

Target: 21:00:00:e0:8b:87:3e:ed

Target Attributes
addr_method PERIPHERAL

explicit_confirmation 0

rel_tgt_id 0

io_grouping_type auto

host /sys/devices/pci0000:00/0000:00:02.0/0000:07:00.3/0000:08:01.0/host3/scsi_host/host3

enabled 0

Target Groups
GROUP: blade1Boot

Group LUN Disk Map
LUN Id. Mapped Device Read Only
0 blade1Boot No

Group Initiators
21:00:00:E0:8B:8E:64:79

I do have a FC swtich and i have added the two WWNs to a new zone.

when I scan for devices from my QL cards bios.. I see nothing.

any thoughts?

thanks for your time..

shane

Questions

Can you post the /etc/scst.conf file?

Also try to use p2p instead of the switch to test if the switch is misconfigured.

sorry for delay..  here is

sorry for delay..  here is the contents of the file..

thanks

 

 

HANDLER vdisk_fileio {
        DEVICE blade1Boot {
                t10_dev_id "blade1Boot 8e9d66e2"
                usn 8e9d66e2

                filename /dev/fc-data/blade1boot
        }
}

TARGET_DRIVER qla2x00t {
        TARGET 21:00:00:e0:8b:87:3e:ed {
                enabled 0

                GROUP blade1Boot {
                        LUN 0 blade1Boot

                        INITIATOR 21:00:00:E0:8B:8E:64:79
                }
        }

        TARGET 21:01:00:e0:8b:a7:3e:ed {
                enabled 0
        }

enabled 0 to enabled 1?

My config looks just like yours, but target is enabled. Is it working for you after turning enabled 0 to enabled 1?

Thanks!
kg6itc@gmail.com
Craig

Enable the targets.

Enable the targets. Both are offline.

Post new comment

The content of this field is kept private and will not be shown publicly.
To prevent automated spam submissions leave this field empty.
By submitting this form, you accept the Mollom privacy policy.