Steps to get iscsi initiator going. 
------------------------------------

1) echo InitiatorName=iqn.1987-05.com.cisco.01.a1ad5447905f8e93a778ddfefedb233 
> /etc/initiatorname.iscsi
2) service open-iscsi start

Then either (manual)
------------------

3.0) iscsiadm -m discovery -t st -p <ip.of.target>

e.g

[EMAIL PROTECTED] ~]# iscsiadm -m discovery -t st -p 192.168.254.10
[1a51c8] 192.168.254.10:3260,1 iqn.2006-01.com.openfiler:dataadd.iscsi

3.1) iscsiadm -m node -r 1a51c8 --login

or (auto)
----------

3.0) conary update open-iscsi
3.1) iscsi_discovery


To have it start on boot:

chkconfig open-iscsi on


That's it. 


R. 



----- Dave Johnson <[EMAIL PROTECTED]> wrote:
> Upon further investigation, it doesn't look like the man page for  
> iscsid.conf(5) even exists yet (?)
> 
> i'll keep plugging away...
> 
> [EMAIL PROTECTED] sbin]# ./iscsid -d8 -f &
> iscsid: IPC socket is listening...
> iscsid: in ctldev_open
> [1] 5535
> [EMAIL PROTECTED] sbin]# iscsid: created NETLINK_ISCSI socket...
> iscsid: InitiatorName=iqn.2006-09.com.openfiler:com.5angle.hq.filer2
> iscsid: no InitiatorAlias found in /etc/initiatorname.iscsi
> iscsid: InitiatorName=iqn.2006-09.com.openfiler:com.5angle.hq.ffiler2
> iscsid: InitiatorAlias=filer2.localdomain
> iscsid: version 0.3 variant (22-Apr-2005)
> iscsid: in ktrans_list
> iscsid: Could not scan /sys/class/iscsi_transport.
> iscsid: failed to get transport list, exiting...
> 
> -=dave
> 
> 
> On Oct 8, 2006, at 4:41 PM, Dave Johnson wrote:
> 
> > Hey Rafiu, i don't think the man page for the iscsid.conf file made 
> 
> > it into the open-iscsi 2.1 trove:
> >
> > [EMAIL PROTECTED] ~]# man iscsid.conf
> > No manual entry for iscsid.conf
> >
> > -=dave
> >
> >
> > On Sep 24, 2006, at 10:30 AM, Rafiu Fakunle wrote:
> >
> >> Hi Joe,
> >>
> >> ----- Joe Landman <[EMAIL PROTECTED]> wrote:
> >>> Hi folks:
> >>>
> >>>   Installed the fresh new beta 2.  Very nice!  The iscsi-target,
> and
> >>> pretty much everything else worked without a hitch.  Good job! 
> My
> >>> OpenSuSE 10.1 iscsi-initiator had kernel-oops in the module, so I
> >>> will
> >>> test with a different system.
> >>>
> >>>   My questions:
> >>>
> >>> 1) How do I make OpenFiler act as an iscsi-initiator?  I didn't
> see
> >>> this
> >>> in the docs.  Is there a document pointer somewhere?
> >>
> >> Not much unfortunately, but it's very easy.
> >>
> >> conary update open-iscsi
> >> man iscsiadm
> >> man iscsid
> >> man iscsid.conf
> >>
> >>
> >>
> >>>
> >>> 2) Will OpenFiler work with SAMBA as the "directory" server?   
> >>> What do
> >>> I
> >>> need to do to make this happen?
> >>
> >> It should in theory. You mean you've got a samba-based PDC
> basically?
> >>
> >>>
> >>> 3) Will OpenFiler eventually provide an x86_64 iso?  I am
> concerned
> >>> about 2TB file size limitations in the 32 bit kernel.
> >>
> >> Yes, I'm just waiting for the dust to settle on 2.1 and then we  
> >> can spin x86_64.
> >>
> >>
> >> R.
> >> _______________________________________________
> >> Openfiler-users mailing list
> >> [email protected]
> >> https://lists.openfiler.com/mailman/listinfo/openfiler-users
> >
> >
> >
> > _______________________________________________
> > Openfiler-users mailing list
> > [email protected]
> > https://lists.openfiler.com/mailman/listinfo/openfiler-users
> 
> 
> 
> _______________________________________________
> Openfiler-users mailing list
> [email protected]
> https://lists.openfiler.com/mailman/listinfo/openfiler-users

_______________________________________________
Openfiler-users mailing list
[email protected]
https://lists.openfiler.com/mailman/listinfo/openfiler-users

Reply via email to