iSCSI Enterprise Target

On Sun, 2005-11-13 at 22:53 -0500, Mike Mazarick wrote:
> Greetings boys and girls!!
> 
> As I pointed out earlier, I finally figured out to turn off the firewall in
> FC4 so that ietd would work with the Windows initiator (thought I'd mention
> it again so others don't try a bunch of other stuff first like I did).  OK,
> so I'm moving on to bigger and better things...

Rather than turning your firewall off completely, creating a hole for
TCP port 3260 should suffice, AFAIK.

> 
> I have also been playing with the Linux iSCSI initiator after playing with
> the Windows one.  It seems like it was not quite as well documented or as
> easy to set up as the ietd target.   For instance, there was an error in the
> source code such that the number of parameters in the variable "__nlmsg_put"
> (which is in several iscsi*.c files) is different than specified by
> netlink.h in the kernel (where it is defined).  The "flags" field needs to
> be set to "0" so that it will compile.  I didn't trace it back far enough to
> know if the kernel file "netlink.h" had changed recently.  I've not noticed
> anything in the mailing lists about this.  I did notice that some familiar
> names around here (like Ming and Fujita) are thanked as part of the testing
> effort.   I also noticed that two initiator projects have been combined into
> one (that's probably a good idea so it can obtain "critical mass").  I have
> been reading with interest that there are two different packages... I have
> been working with the "version 5, latest and greatest" and haven't noticed
> that.
> 
> I'm using the packages as specified in the SourceForge page:
> http://sourceforge.net/projects/linux-iscsi
> 
> Is this what everyone else is using for a linux iSCSI initiator?  Are there

I've been using linux-iscsi-3.6, which is included in RHEL 3 (U5+) and
linux-iscsi-4.0 which is included in RHEL4 (U2+).

> instructions for this particular software package that will show you how to
> boot diskless (that are good)?  What has been other people's experiences

I've created a custom mkinitrd-iscsi tool for booting the diskless
servers in our datacenter.  Besides regular diskless boot it supports
some high availability features like mirroring the root fs on two
iscsi-targets and bonding ethernet.
Currently it supports RHEL3 only (RHEL4 is in the works), but now that
open-iscsi is merged in the kernel I hope to be able to port to
FC5-devel soon.
I you are interested let me know.

> with this package?  Is this the same package that has been put in the
> official linux kernel?

Yes and no :-) 
Last week iSCSI initiator code from the open-iscsi project has been
merged into 2.6.15rc1. This code is different from the linux-iscsi code
in RHEL3 and RHEL4. But last spring the linux-iscsi and open-iscsi
projects have merged and decided to continue with the open-iscsi code.
So linux-iscsi-5 code is equivalent to open-iscsi.
 
Regards,

Bastiaan

> 
> Regards,
> 
> Mike Mazarick
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Iscsitarget-devel mailing list
> Iscsitarget-devel@...
> https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel

I'd be very interested in a simple guide as to how you do this (the
booting off iscsi/bonding bit).

Greg


On Mon, 2005-11-14 at 10:27 +0100, Bastiaan Bakker wrote:
> On Sun, 2005-11-13 at 22:53 -0500, Mike Mazarick wrote:
> > Greetings boys and girls!!
> > 
> > As I pointed out earlier, I finally figured out to turn off the firewall in
> > FC4 so that ietd would work with the Windows initiator (thought I'd mention
> > it again so others don't try a bunch of other stuff first like I did).  OK,
> > so I'm moving on to bigger and better things...
> 
> Rather than turning your firewall off completely, creating a hole for
> TCP port 3260 should suffice, AFAIK.
> 
> > 
> > I have also been playing with the Linux iSCSI initiator after playing with
> > the Windows one.  It seems like it was not quite as well documented or as
> > easy to set up as the ietd target.   For instance, there was an error in the
> > source code such that the number of parameters in the variable "__nlmsg_put"
> > (which is in several iscsi*.c files) is different than specified by
> > netlink.h in the kernel (where it is defined).  The "flags" field needs to
> > be set to "0" so that it will compile.  I didn't trace it back far enough to
> > know if the kernel file "netlink.h" had changed recently.  I've not noticed
> > anything in the mailing lists about this.  I did notice that some familiar
> > names around here (like Ming and Fujita) are thanked as part of the testing
> > effort.   I also noticed that two initiator projects have been combined into
> > one (that's probably a good idea so it can obtain "critical mass").  I have
> > been reading with interest that there are two different packages... I have
> > been working with the "version 5, latest and greatest" and haven't noticed
> > that.
> > 
> > I'm using the packages as specified in the SourceForge page:
> > http://sourceforge.net/projects/linux-iscsi
> > 
> > Is this what everyone else is using for a linux iSCSI initiator?  Are there
> 
> I've been using linux-iscsi-3.6, which is included in RHEL 3 (U5+) and
> linux-iscsi-4.0 which is included in RHEL4 (U2+).
> 
> > instructions for this particular software package that will show you how to
> > boot diskless (that are good)?  What has been other people's experiences
> 
> I've created a custom mkinitrd-iscsi tool for booting the diskless
> servers in our datacenter.  Besides regular diskless boot it supports
> some high availability features like mirroring the root fs on two
> iscsi-targets and bonding ethernet.
> Currently it supports RHEL3 only (RHEL4 is in the works), but now that
> open-iscsi is merged in the kernel I hope to be able to port to
> FC5-devel soon.
> I you are interested let me know.
> 
> > with this package?  Is this the same package that has been put in the
> > official linux kernel?
> 
> Yes and no :-) 
> Last week iSCSI initiator code from the open-iscsi project has been
> merged into 2.6.15rc1. This code is different from the linux-iscsi code
> in RHEL3 and RHEL4. But last spring the linux-iscsi and open-iscsi
> projects have merged and decided to continue with the open-iscsi code.
> So linux-iscsi-5 code is equivalent to open-iscsi.
>  
> Regards,
> 
> Bastiaan
> 
> > 
> > Regards,
> > 
> > Mike Mazarick
> > 
> > 
> > 
> > -------------------------------------------------------
> > SF.Net email is sponsored by:
> > Tame your development challenges with Apache's Geronimo App Server. Download
> > it for free - -and be entered to win a 42" plasma tv or your very own
> > Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> > _______________________________________________
> > Iscsitarget-devel mailing list
> > Iscsitarget-devel@...
> > https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Iscsitarget-devel mailing list
> Iscsitarget-devel@...
> https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel

On Mon, 2005-11-14 at 09:48 +0000, Greg Cope wrote:
> I'd be very interested in a simple guide as to how you do this (the
> booting off iscsi/bonding bit).
> 

yes, i think put on iet or open-iscsi wiki will be interesting and
useful. thanks

ming

> Greg
> 
> 
> On Mon, 2005-11-14 at 10:27 +0100, Bastiaan Bakker wrote:
> > On Sun, 2005-11-13 at 22:53 -0500, Mike Mazarick wrote:
> > > Greetings boys and girls!!
> > > 
> > > As I pointed out earlier, I finally figured out to turn off the firewall in
> > > FC4 so that ietd would work with the Windows initiator (thought I'd mention
> > > it again so others don't try a bunch of other stuff first like I did).  OK,
> > > so I'm moving on to bigger and better things...
> > 
> > Rather than turning your firewall off completely, creating a hole for
> > TCP port 3260 should suffice, AFAIK.
> > 
> > > 
> > > I have also been playing with the Linux iSCSI initiator after playing with
> > > the Windows one.  It seems like it was not quite as well documented or as
> > > easy to set up as the ietd target.   For instance, there was an error in the
> > > source code such that the number of parameters in the variable "__nlmsg_put"
> > > (which is in several iscsi*.c files) is different than specified by
> > > netlink.h in the kernel (where it is defined).  The "flags" field needs to
> > > be set to "0" so that it will compile.  I didn't trace it back far enough to
> > > know if the kernel file "netlink.h" had changed recently.  I've not noticed
> > > anything in the mailing lists about this.  I did notice that some familiar
> > > names around here (like Ming and Fujita) are thanked as part of the testing
> > > effort.   I also noticed that two initiator projects have been combined into
> > > one (that's probably a good idea so it can obtain "critical mass").  I have
> > > been reading with interest that there are two different packages... I have
> > > been working with the "version 5, latest and greatest" and haven't noticed
> > > that.
> > > 
> > > I'm using the packages as specified in the SourceForge page:
> > > http://sourceforge.net/projects/linux-iscsi
> > > 
> > > Is this what everyone else is using for a linux iSCSI initiator?  Are there
> > 
> > I've been using linux-iscsi-3.6, which is included in RHEL 3 (U5+) and
> > linux-iscsi-4.0 which is included in RHEL4 (U2+).
> > 
> > > instructions for this particular software package that will show you how to
> > > boot diskless (that are good)?  What has been other people's experiences
> > 
> > I've created a custom mkinitrd-iscsi tool for booting the diskless
> > servers in our datacenter.  Besides regular diskless boot it supports
> > some high availability features like mirroring the root fs on two
> > iscsi-targets and bonding ethernet.
> > Currently it supports RHEL3 only (RHEL4 is in the works), but now that
> > open-iscsi is merged in the kernel I hope to be able to port to
> > FC5-devel soon.
> > I you are interested let me know.
> > 
> > > with this package?  Is this the same package that has been put in the
> > > official linux kernel?
> > 
> > Yes and no :-) 
> > Last week iSCSI initiator code from the open-iscsi project has been
> > merged into 2.6.15rc1. This code is different from the linux-iscsi code
> > in RHEL3 and RHEL4. But last spring the linux-iscsi and open-iscsi
> > projects have merged and decided to continue with the open-iscsi code.
> > So linux-iscsi-5 code is equivalent to open-iscsi.
> >  
> > Regards,
> > 
> > Bastiaan
> > 
> > > 
> > > Regards,
> > > 
> > > Mike Mazarick
> > > 
> > > 
> > > 
> > > -------------------------------------------------------
> > > SF.Net email is sponsored by:
> > > Tame your development challenges with Apache's Geronimo App Server. Download
> > > it for free - -and be entered to win a 42" plasma tv or your very own
> > > Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> > > _______________________________________________
> > > Iscsitarget-devel mailing list
> > > Iscsitarget-devel@...
> > > https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel
> > 
> > 
> > -------------------------------------------------------
> > SF.Net email is sponsored by:
> > Tame your development challenges with Apache's Geronimo App Server. Download
> > it for free - -and be entered to win a 42" plasma tv or your very own
> > Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> > _______________________________________________
> > Iscsitarget-devel mailing list
> > Iscsitarget-devel@...
> > https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Iscsitarget-devel mailing list
> Iscsitarget-devel@...
> https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel

On Mon, 2005-11-14 at 09:48 +0000, Greg Cope wrote:
> I'd be very interested in a simple guide as to how you do this (the
> booting off iscsi/bonding bit).

Well, basically the initrd is a modified version of the disklessrc for
NFS root systems in the system-config-netboot package. It does DHCP,
sets up the network interfaces, starts up iscsid, inits RAD and finally
switches to the new root filesystem.
I'll try to publish the mkinitrd-iscsi and admin RPMs and preliminary
documentation tomorrow or at least this week.

Bastiaan
 
> 
> Greg
> 
> 
> On Mon, 2005-11-14 at 10:27 +0100, Bastiaan Bakker wrote:
> > On Sun, 2005-11-13 at 22:53 -0500, Mike Mazarick wrote:
> > > Greetings boys and girls!!
> > > 
> > > As I pointed out earlier, I finally figured out to turn off the firewall in
> > > FC4 so that ietd would work with the Windows initiator (thought I'd mention
> > > it again so others don't try a bunch of other stuff first like I did).  OK,
> > > so I'm moving on to bigger and better things...
> > 
> > Rather than turning your firewall off completely, creating a hole for
> > TCP port 3260 should suffice, AFAIK.
> > 
> > > 
> > > I have also been playing with the Linux iSCSI initiator after playing with
> > > the Windows one.  It seems like it was not quite as well documented or as
> > > easy to set up as the ietd target.   For instance, there was an error in the
> > > source code such that the number of parameters in the variable "__nlmsg_put"
> > > (which is in several iscsi*.c files) is different than specified by
> > > netlink.h in the kernel (where it is defined).  The "flags" field needs to
> > > be set to "0" so that it will compile.  I didn't trace it back far enough to
> > > know if the kernel file "netlink.h" had changed recently.  I've not noticed
> > > anything in the mailing lists about this.  I did notice that some familiar
> > > names around here (like Ming and Fujita) are thanked as part of the testing
> > > effort.   I also noticed that two initiator projects have been combined into
> > > one (that's probably a good idea so it can obtain "critical mass").  I have
> > > been reading with interest that there are two different packages... I have
> > > been working with the "version 5, latest and greatest" and haven't noticed
> > > that.
> > > 
> > > I'm using the packages as specified in the SourceForge page:
> > > http://sourceforge.net/projects/linux-iscsi
> > > 
> > > Is this what everyone else is using for a linux iSCSI initiator?  Are there
> > 
> > I've been using linux-iscsi-3.6, which is included in RHEL 3 (U5+) and
> > linux-iscsi-4.0 which is included in RHEL4 (U2+).
> > 
> > > instructions for this particular software package that will show you how to
> > > boot diskless (that are good)?  What has been other people's experiences
> > 
> > I've created a custom mkinitrd-iscsi tool for booting the diskless
> > servers in our datacenter.  Besides regular diskless boot it supports
> > some high availability features like mirroring the root fs on two
> > iscsi-targets and bonding ethernet.
> > Currently it supports RHEL3 only (RHEL4 is in the works), but now that
> > open-iscsi is merged in the kernel I hope to be able to port to
> > FC5-devel soon.
> > I you are interested let me know.
> > 
> > > with this package?  Is this the same package that has been put in the
> > > official linux kernel?
> > 
> > Yes and no :-) 
> > Last week iSCSI initiator code from the open-iscsi project has been
> > merged into 2.6.15rc1. This code is different from the linux-iscsi code
> > in RHEL3 and RHEL4. But last spring the linux-iscsi and open-iscsi
> > projects have merged and decided to continue with the open-iscsi code.
> > So linux-iscsi-5 code is equivalent to open-iscsi.
> >  
> > Regards,
> > 
> > Bastiaan
> > 
> > > 
> > > Regards,
> > > 
> > > Mike Mazarick
> > > 
> > > 
> > > 
> > > -------------------------------------------------------
> > > SF.Net email is sponsored by:
> > > Tame your development challenges with Apache's Geronimo App Server. Download
> > > it for free - -and be entered to win a 42" plasma tv or your very own
> > > Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> > > _______________________________________________
> > > Iscsitarget-devel mailing list
> > > Iscsitarget-devel@...
> > > https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel
> > 
> > 
> > -------------------------------------------------------
> > SF.Net email is sponsored by:
> > Tame your development challenges with Apache's Geronimo App Server. Download
> > it for free - -and be entered to win a 42" plasma tv or your very own
> > Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> > _______________________________________________
> > Iscsitarget-devel mailing list
> > Iscsitarget-devel@...
> > https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Iscsitarget-devel mailing list
> Iscsitarget-devel@...
> https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel

On 2005.11.14 22:31:52 +0000, Bastiaan Bakker wrote:
> On Mon, 2005-11-14 at 09:48 +0000, Greg Cope wrote:
> > I'd be very interested in a simple guide as to how you do this (the
> > booting off iscsi/bonding bit).
> 
> Well, basically the initrd is a modified version of the disklessrc for
> NFS root systems in the system-config-netboot package. It does DHCP,
> sets up the network interfaces, starts up iscsid, inits RAD and finally
> switches to the new root filesystem.
> I'll try to publish the mkinitrd-iscsi and admin RPMs and preliminary
> documentation tomorrow or at least this week.

Great! Have you tried to make it work with open-iscsi? I wanna help on that
one. And another thing is PXE boot, using pxelinux and tftp seems "that should
be working" for me, anyone has experience on this?

zhen

> 
> Bastiaan
>  
> > 
> > Greg
> > 
> > 
> > On Mon, 2005-11-14 at 10:27 +0100, Bastiaan Bakker wrote:
> > > On Sun, 2005-11-13 at 22:53 -0500, Mike Mazarick wrote:
> > > > Greetings boys and girls!!
> > > > 
> > > > As I pointed out earlier, I finally figured out to turn off the firewall in
> > > > FC4 so that ietd would work with the Windows initiator (thought I'd mention
> > > > it again so others don't try a bunch of other stuff first like I did).  OK,
> > > > so I'm moving on to bigger and better things...
> > > 
> > > Rather than turning your firewall off completely, creating a hole for
> > > TCP port 3260 should suffice, AFAIK.
> > > 
> > > > 
> > > > I have also been playing with the Linux iSCSI initiator after playing with
> > > > the Windows one.  It seems like it was not quite as well documented or as
> > > > easy to set up as the ietd target.   For instance, there was an error in the
> > > > source code such that the number of parameters in the variable "__nlmsg_put"
> > > > (which is in several iscsi*.c files) is different than specified by
> > > > netlink.h in the kernel (where it is defined).  The "flags" field needs to
> > > > be set to "0" so that it will compile.  I didn't trace it back far enough to
> > > > know if the kernel file "netlink.h" had changed recently.  I've not noticed
> > > > anything in the mailing lists about this.  I did notice that some familiar
> > > > names around here (like Ming and Fujita) are thanked as part of the testing
> > > > effort.   I also noticed that two initiator projects have been combined into
> > > > one (that's probably a good idea so it can obtain "critical mass").  I have
> > > > been reading with interest that there are two different packages... I have
> > > > been working with the "version 5, latest and greatest" and haven't noticed
> > > > that.
> > > > 
> > > > I'm using the packages as specified in the SourceForge page:
> > > > http://sourceforge.net/projects/linux-iscsi
> > > > 
> > > > Is this what everyone else is using for a linux iSCSI initiator?  Are there
> > > 
> > > I've been using linux-iscsi-3.6, which is included in RHEL 3 (U5+) and
> > > linux-iscsi-4.0 which is included in RHEL4 (U2+).
> > > 
> > > > instructions for this particular software package that will show you how to
> > > > boot diskless (that are good)?  What has been other people's experiences
> > > 
> > > I've created a custom mkinitrd-iscsi tool for booting the diskless
> > > servers in our datacenter.  Besides regular diskless boot it supports
> > > some high availability features like mirroring the root fs on two
> > > iscsi-targets and bonding ethernet.
> > > Currently it supports RHEL3 only (RHEL4 is in the works), but now that
> > > open-iscsi is merged in the kernel I hope to be able to port to
> > > FC5-devel soon.
> > > I you are interested let me know.
> > > 
> > > > with this package?  Is this the same package that has been put in the
> > > > official linux kernel?
> > > 
> > > Yes and no :-) 
> > > Last week iSCSI initiator code from the open-iscsi project has been
> > > merged into 2.6.15rc1. This code is different from the linux-iscsi code
> > > in RHEL3 and RHEL4. But last spring the linux-iscsi and open-iscsi
> > > projects have merged and decided to continue with the open-iscsi code.
> > > So linux-iscsi-5 code is equivalent to open-iscsi.
> > >  
> > > Regards,
> > > 
> > > Bastiaan
> > > 
> > > > 
> > > > Regards,
> > > > 
> > > > Mike Mazarick
> > > > 
> > > > 
> > > > 
> > > > -------------------------------------------------------
> > > > SF.Net email is sponsored by:
> > > > Tame your development challenges with Apache's Geronimo App Server. Download
> > > > it for free - -and be entered to win a 42" plasma tv or your very own
> > > > Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> > > > _______________________________________________
> > > > Iscsitarget-devel mailing list
> > > > Iscsitarget-devel@...
> > > > https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel
> > > 
> > > 
> > > -------------------------------------------------------
> > > SF.Net email is sponsored by:
> > > Tame your development challenges with Apache's Geronimo App Server. Download
> > > it for free - -and be entered to win a 42" plasma tv or your very own
> > > Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> > > _______________________________________________
> > > Iscsitarget-devel mailing list
> > > Iscsitarget-devel@...
> > > https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel
> > 
> > 
> > 
> > -------------------------------------------------------
> > SF.Net email is sponsored by:
> > Tame your development challenges with Apache's Geronimo App Server. Download
> > it for free - -and be entered to win a 42" plasma tv or your very own
> > Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> > _______________________________________________
> > Iscsitarget-devel mailing list
> > Iscsitarget-devel@...
> > https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Iscsitarget-devel mailing list
> Iscsitarget-devel@...
> https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel

On Tue, 2005-11-15 at 14:11 +0800, Wang Zhenyu wrote:
> On 2005.11.14 22:31:52 +0000, Bastiaan Bakker wrote:
> > On Mon, 2005-11-14 at 09:48 +0000, Greg Cope wrote:
> > > I'd be very interested in a simple guide as to how you do this (the
> > > booting off iscsi/bonding bit).
> > 
> > Well, basically the initrd is a modified version of the disklessrc for
> > NFS root systems in the system-config-netboot package. It does DHCP,
> > sets up the network interfaces, starts up iscsid, inits RAD and finally
> > switches to the new root filesystem.
> > I'll try to publish the mkinitrd-iscsi and admin RPMs and preliminary
> > documentation tomorrow or at least this week.
> 
> Great! Have you tried to make it work with open-iscsi? I wanna help on that

No, I haven't yet. RHEL3 and RHEL4 (which both use linux-iscsi) had
higher priority. 
But Fedora and RHEL5 will be open-iscsi based, so I'd like to get that
working too. If you want to help, great!

> one. And another thing is PXE boot, using pxelinux and tftp seems "that should
> be working" for me, anyone has experience on this?
> 

Yes, the setup in our datacenter uses pxelinux and tftp to get the
kernel and initrd to the diskless servers. Works fine. We've written a
simple command line tool to admin the DHCP config, so operators can
simply do 'iscsi-boot-admin replace-server <broken-server>
<spare-server>' to replace failing hardware.

Regards,

Bastiaan

On Tue, 2005-11-15 at 07:57 +0100, Bastiaan Bakker wrote:
> On Tue, 2005-11-15 at 14:11 +0800, Wang Zhenyu wrote:
> > On 2005.11.14 22:31:52 +0000, Bastiaan Bakker wrote:
> > > On Mon, 2005-11-14 at 09:48 +0000, Greg Cope wrote:
> > > > I'd be very interested in a simple guide as to how you do this (the
> > > > booting off iscsi/bonding bit).
> > > 
> > > Well, basically the initrd is a modified version of the disklessrc for
> > > NFS root systems in the system-config-netboot package. It does DHCP,
> > > sets up the network interfaces, starts up iscsid, inits RAD and finally
> > > switches to the new root filesystem.
> > > I'll try to publish the mkinitrd-iscsi and admin RPMs and preliminary
> > > documentation tomorrow or at least this week.

That would be great.
 
> > one. And another thing is PXE boot, using pxelinux and tftp seems "that should
> > be working" for me, anyone has experience on this?

I do all my installs with kickstart and pxeboot - saves swapping CD's
and lots of other things.

Greg

> Regards,
> 
> Bastiaan
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
> Register for a JBoss Training Course.  Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
> _______________________________________________
> Iscsitarget-devel mailing list
> Iscsitarget-devel@...
> https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel