Hi, open fcoe buddies
I'm engineer in China who would like to set lio iscsi target enviroment
on redhat 6.4 server. But encountered problems. So may you do a quick answer
according to your expertise ?
Below is what I have done try to set up the lio iscsi target enviroment on
redhat 6.4 server:
1. download original 3.6.0 kernel tar ball and make out the bzImage and
install the modules of 3.6.0(use the original redhat 6.4 kernel config file
under boot, and choose on the iscsi target mod which is new is 3.6.0). Then
boot to linux with 3.6.0 kernel image and its lib(kernel modules) via do the
little change in the /etc/grub.conf.
2. remove out three rpms in the original redhat
6.4(python-rtslib-1.1.fb4-1.e16.norch, python-configshell-2.1.fb21-1.e16.norch
and fcoe-target-utils-2.0rc1.fb16-3.e16.norch). And install three new
rpms(python-rtslib-fb-2.1.fb37-5.2.norch,
python-configshell-fb-1.1.fb8-9.1.norch and targetcli-fb-2.1.fb28-14.1.norch)
according to below description in the wiki link
https://wiki.archlinux.org/index.php/ISCSI_Target
/etc/rc.d/target is included in targetcli-fb when you use the free
branch or a less clean version in lio-utils when you use the original targetcli
or lio-utilsdirectly.
With these two steps I can see below surface after installed nessary
modules(include iscsi_target_mod), and mount the configfs on
/sys/kernel/config. The iscsi folder appears:)
/> ls
o- / ..................................................................... [...]
o- backstores .......................................................... [...]
| o- fileio ............................................... [0 Storage Object]
| o- iblock .............................................. [0 Storage Objects]
| o- pscsi ................................................ [0 Storage Object]
| o- ramdisk ................................................ [0 Storage Object]
o- iscsi .......................................................... [0 Target]
o- loopback ....................................................... [0 Target]
/>
I can create iscsi target via iscsi folder. But problem is when I tried to
create fileio files it showed like below error "Can not set attribute
emulate_write_cache error" And no fileio file created.
1. So do you have ideas how to solve this problem?
2. Or would you do me a little guide how to better set up lio iscsi target
enviroment on redhat 6.4 server?
3. If you do not have ideas of upstairs two questions, would you show me some
email(or which community) who I can get help?
Thanks very much in advance,
Qiuping
At 2013-09-17 17:29:25,luqiuping_zju <[email protected]> wrote:
Thanks Rob, Ken and Gondi for great support!
I have fortunately finally set the end to end fcoe system up:-)
Below message do mislead me much during the setup and thanks for clarification.
Especially thanks to Rob for you great expertise and it's my honor to get
response from you! You are the architecture of open fcoe as I know:-)
I missed the zone related setups in cisco switch side cause former setup fail.
Thanks,
Qiuping
At 2013-09-14 05:19:21,"Prasad Gondi" <[email protected]> wrote:
>I was able to setup the FCoE target using x520 Niantec adapter connected to
>Nexus 5020 FCoE switch in our lab successfully about a year back. Target
>driver is FCST which I downloaded from
>http://scst.sourceforge.net/target_fcoe.html and driver is IXGBE. I have
>created a README file at that time which is based on fcst read-me with
>detailed steps to re-create the FCoE target again. Hope this helps, please
>find the attached readme doc.
>
>Thanks,
>Prasad
>
>----- Original Message -----
>From: "Kenneth Zhang" <[email protected]>
>To: "Robert W Love" <[email protected]>, "luqiuping_zju"
><[email protected]>, [email protected]
>Sent: Friday, September 13, 2013 2:00:58 PM
>Subject: Re: [Open-FCoE] Fw:Can intel x520 network adapter use as fcoe
>target?
>
>The description regarding target mode of Intel adapter and Qlogic adapter in
>that document is misleading. The fact is that Netapp uses Qlogic adapter in
>its storage device, not that Intel X520 does not support target mode.
>
>In your case, after you installed fcoe-target-utils, the same physical
>interface is running as an Initiator as well as a target concurrently; they
>should share the same fcid. Since you can get fcid for initiator, you should
>also get fcid for the target.
>
>Can you do trouble shooting:
>- swap cable between initiator and target and see you can get fcid on target
>but not on initiator; if yes, you may have config issue in the switch, if not
>you may have config issue in the target
>- check switch port to see PFC operation is "ON" or maybe other setups
>- check DCB setting on the target system with dcbtool and lldptool
>
>Thanks, Ken
>
>-----Original Message-----
>From: [email protected]
>[mailto:[email protected]] On Behalf Of Love, Robert W
>Sent: Friday, September 13, 2013 1:10 PM
>To: luqiuping_zju; [email protected]
>Subject: Re: [Open-FCoE] Fw:Can intel x520 network adapter use as fcoe target?
>
>I contacted the document owner and it is simply out of date. The FCoE target
>should work fine on x520. The RH document should work just fine.
>
>I am unsure why you're not getting an FCID. Are the VLAN and FCF being
>discovered correctly?
>
>It's likely to just be a configuration problem. If the log file isn't
>providing details as to why, you could take a wire trace to see what's
>happening on the wire or turn on debug_logging to see if there are any clues
>with extra verbosity.
>
>//Rob
>
>From: luqiuping_zju [mailto:[email protected]]
>Sent: Wednesday, September 11, 2013 3:03 AM
>To: Love, Robert W; [email protected]
>Subject: Fw:Can intel x520 network adapter use as fcoe target?
>
>HI, Open fcoe team
> I'm one eigneer in China who would like to set up end-to-end fcoe to
> run fcoe traffic. But I have trouble when try to set up fcoe target on the
> x520 adaptor. So I have question if x520 network adaptoer can be used as fcoe
> target?
>
> I'm trying to setup end-to-end fcoe via below enviroment:
> server->cisco switch->storage
> server enviroment: original HP server installed with x520 network
> adaper. Run as fcoe initiator. Software enviroment redhat 6.4. Fcoe-utils
> software installed.
> cisco switch: cisco 5000 series nexus 5548P switch
> storage: exactly the same hardware as server. also original HP
> server installed with x520 adapter. Run as fcoe initiator. Software
> enviroment 6.4. fcoe-target-utils software installed.
>
> I have followeed below steps in the redhat fcoe setup release note.
> https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/fcoeconfig.html
> The fcoe initiator can be set up successfully via intel x520 network
> adapter. "fcoeadm -i" would show the exactly the fcoe device online. The
> connection setup with Cisco switch successfully.
> But the fcoe target with intel x520 adapter can't via the steps in the
> link upstairs. "fcoeadm -i" wouldn't show the fcoe device online in target
> side. Either in cisco switch would not see the target fcid.
>
> Below there question would you help do an answer.
> 1. So I'm wondering if x520 server can support fcoe target? Does it
> mean x520 adapter could not used as a fcoe target? There is one such
> description in the attachment technical document(Intel Cloud Builders_Unified
> Networking_FCOE.pdf) written by intel.
> Since the Intel Ethernet Server Adapter x520 does not support a FCoE
> Target, Qlogic FCoE cards are used for access.
> 2. If intel fcoe card can be used as fcoe target, would you give me
> hints how to set it up?
> 3. If intel fcoe card can't be used as fcoe target, would you show me
> which Qlogic fcoe cards cards can be used as fcoe target?
>
> I would provide more info if you need.
>
> Great thanks in advance,
> Qiuping
>
>
>
>
>
>
>_______________________________________________
>fcoe-devel mailing list
>[email protected]
>http://lists.open-fcoe.org/mailman/listinfo/fcoe-devel
>_______________________________________________
>fcoe-devel mailing list
>[email protected]
>http://lists.open-fcoe.org/mailman/listinfo/fcoe-devel
_______________________________________________
fcoe-devel mailing list
[email protected]
http://lists.open-fcoe.org/mailman/listinfo/fcoe-devel
