fully automatically installation
Hi, at the moment our installserver is running quite good. What I don't like is going to every machine as soon a reinstall is necessary. So what do I plan to do: I want every client to start up and check whether he needs to be installed or not (best including wake up on lan). Ok this is the main aim and want to realise it step by step. Thinking of the following: There is one bootp/tftp, dhcp and/or PXE Server running. And for sure the installserver itself. My problem is now. What do I need PXE or only dhcp and tftp. And how to set it up. The first aim would be to get a full networkinstall without any boot media. Thanks in advanced for all your suggestions. cheers frank +----------------------------------------------------------+ | Max-Planck-Institut für Radioastronomie | | Abt.1 (wissenschaftliche DV) | | | | Frank Pascher | +----------------------------------------------------------+ | Auf dem Huegel 69 Tel.: +49 (228) 525 359 | | 53121 Bonn Fax.: +49 (228) 535 229 | +----------------------------------------------------------+ | Email: mailto:fpascher@mpifr-bonn.mpg.de | | WWW: http://www.mpifr-bonn.mpg.de | | PGP Fingerprint: 13D1 8C86 57B3 2850 F158 4879 E5F3 7E20 | +----------------------------------------------------------+
* Frank Pascher <fpascher@mpifr-bonn.mpg.de> [Jul 04. 2002 18:24]:
at the moment our installserver is running quite good. What I don't like is going to every machine as soon a reinstall is necessary. So what do I plan to do:
Why do you need to go to the machine?
I want every client to start up and check whether he needs to be installed or not (best including wake up on lan). Ok this is the main aim and want to realise it step by step.
Thinking of the following: There is one bootp/tftp, dhcp and/or PXE Server running. And for sure the installserver itself. My problem is now. What do I need PXE or only dhcp and tftp.
If you are going to use PXELINUX (Syslinux) then you will always need tftp and dhcp server running on the installation server or somewhere else. (Actually the combination of the three is always needed, nevermind which PXE implementation you need).
And how to set it up. The first aim would be to get a full networkinstall without any boot media.
This already possible and should not be a problem to setup! What exactly do you want to know?
Thanks in advanced for all your suggestions.
cheers frank
Anas
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com -- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
Hi Anas
-----Ursprüngliche Nachricht----- Von: Anas Nashif [mailto:nashif@suse.de] Gesendet: Freitag, 5. Juli 2002 04:42 An: Frank Pascher Cc: suse-autoinstall@suse.com Betreff: Re: [suse-autoinstall] fully automatically installation
* Frank Pascher <fpascher@mpifr-bonn.mpg.de> [Jul 04. 2002 18:24]:
at the moment our installserver is running quite good. What I don't like is going to every machine as soon a reinstall is necessary. So what do I plan to do:
Why do you need to go to the machine?
Actually to start up the machine, type in the parameters for install and repository and boot the initial system bevore the server takes over.
I want every client to start up and check whether he needs to be installed or not (best including wake up on lan). Ok this is the main aim and want to realise it step by step.
Thinking of the following: There is one bootp/tftp, dhcp and/or PXE Server running. And for sure the installserver itself. My problem is now. What do I need PXE or only dhcp and tftp.
If you are going to use PXELINUX (Syslinux) then you will always need tftp and dhcp server running on the installation server or somewhere else. (Actually the combination of the three is always needed, nevermind which PXE implementation you need).
And how to set it up. The first aim would be to get a full networkinstall without any boot media.
This already possible and should not be a problem to setup! What exactly do you want to know?
OK, I know that it is possible to work with a dhcp server, but getting a little bit confused about the protocolls networkcards can do. Lots of our machine have lan on board but run ipx and not tcp or pxe. Now I need to know how to get these clients doing a network boot. As a result of this I try to set a standard for networkcards in our institute. On checking the cardsdefinitions the confusion started. So what protocol do I need. I don't get the differences of pxe and the rest. The next problem is the following. There is one dhcp server existing who serves every computer running dhcp and not being managed by the computercenter. I don't want to work with that machine. How do I set up a second dhcp server which serves the linux installation clients only. Am I right, that it would be the best setting up a new server and canceling the old one ??
Thanks in advanced for all your suggestions.
cheers frank
Anas
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com -- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
cheers frank
* Frank Pascher <fpascher@mpifr-bonn.mpg.de> [Jul 05. 2002 09:09]:
Hi Anas
-----Ursprüngliche Nachricht----- Von: Anas Nashif [mailto:nashif@suse.de] Gesendet: Freitag, 5. Juli 2002 04:42 An: Frank Pascher Cc: suse-autoinstall@suse.com Betreff: Re: [suse-autoinstall] fully automatically installation
Why do you need to go to the machine?
Actually to start up the machine, type in the parameters for install and repository and boot the initial system bevore the server takes over.
No need for that if you use PXE or netboot/etherboot, but I guess this is the problem you are trying to solve :-)
This already possible and should not be a problem to setup! What exactly do you want to know?
OK, I know that it is possible to work with a dhcp server, but getting a little bit confused about the protocolls networkcards can do. Lots of our machine have lan on board but run ipx and not tcp or pxe. Now I need to know how to get these clients doing a network boot. As a result of this I try to set a standard for networkcards in our institute. On checking the cardsdefinitions the confusion started. So what protocol do I need. I don't get the differences of pxe and the rest.
The next problem is the following. There is one dhcp server existing who serves every computer running dhcp and not being managed by the computercenter. I don't want to work with that machine. How do I set up a second dhcp server which serves the linux installation clients only. Am I right, that it would be the best setting up a new server and canceling the old one ??
Depending on the hardware you have (NICs), I am aware of 2 ways to make things work in an automated way using network boot. Either your NICs have PXE on them, then you can use PXELINUX (http://syslinux.zytor.com/pxe.php) Or you can use etherboot and flash all NICs with a boot image, maybe those NICs have an EPROM already... If your NICs support network boot, then you can pass all needed variables via dhcp, boot image is transfered to the clients using tftp. So it's a matter of what hardware you have.,... Anas -- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
Hi Anas
-----Ursprüngliche Nachricht----- Von: Anas Nashif [mailto:nashif@suse.de] Gesendet: Freitag, 5. Juli 2002 17:47 An: Frank Pascher Cc: suse-autoinstall@suse.com Betreff: Re: AW: [suse-autoinstall] fully automatically installation
* Frank Pascher <fpascher@mpifr-bonn.mpg.de> [Jul 05. 2002 09:09]:
Hi Anas
-----Ursprüngliche Nachricht----- Von: Anas Nashif [mailto:nashif@suse.de] Gesendet: Freitag, 5. Juli 2002 04:42 An: Frank Pascher Cc: suse-autoinstall@suse.com Betreff: Re: [suse-autoinstall] fully automatically installation
Why do you need to go to the machine?
Actually to start up the machine, type in the parameters for install and repository and boot the initial system bevore the server takes over.
No need for that if you use PXE or netboot/etherboot, but I guess this is the problem you are trying to solve :-)
you are right :-))
This already possible and should not be a problem to setup! What exactly do you want to know?
OK, I know that it is possible to work with a dhcp server, but getting a little bit confused about the protocolls networkcards can do. Lots of our machine have lan on board but run ipx and not tcp or pxe. Now I need to know how to get these clients doing a network boot. As a result of this I try to set a standard for networkcards in our institute. On checking the cardsdefinitions the confusion started. So what protocol do I need. I don't get the differences of pxe and the rest.
The next problem is the following. There is one dhcp server existing who serves every computer running dhcp and not being managed by the computercenter. I don't want to work with that machine. How do I set up a second dhcp server which serves the linux installation clients only. Am I right, that it would be the best setting up a new server and canceling the old one ??
Depending on the hardware you have (NICs), I am aware of 2 ways to make things work in an automated way using network boot. Either your NICs have PXE on them, then you can use PXELINUX (http://syslinux.zytor.com/pxe.php) Or you can use etherboot and flash all NICs with a boot image, maybe those NICs have an EPROM already...
If your NICs support network boot, then you can pass all needed variables via dhcp, boot image is transfered to the clients using tftp. So it's a matter of what hardware you have.,...
Are there any suggestions concerning network cards. So far I found 3com 3C905CX-TX-M. According to the technical data sheet this card should be OK. Is this OK and do you know other working cards for this job ?? Cheers frank
participants (2)
-
Anas Nashif -
Frank Pascher