Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BladeServer HS20 and BootP

Status
Not open for further replies.

klaxyn

Technical User
Jul 16, 2000
21
0
0
US
I'm trying to setup our IBM BladeServer (HS20) to boot over the networking using dhcp and netboot from a linux box. Does anyone have any experience with this? Right now I'm stuck trying to build a kernel image with makerom. I downloaded the broadcom drivers from the broadcom site but makerom says they are 'too big'. Any information about setting up a netboot environment would be helpful. I've found lots of information on the web but nothing too specific.

Thanks!

Kurin Lambert
klambert@earthmatrix.org
 
Hi

I can't help you directly with your linux question, but
You may find a better option may be to purchase IBM remote deployment manager which is well suited to the blade servers.
This would Automate your image creation for linux.
At least have a read up on it if you have not done so and see what you think.. IBM RDM.

Hope this helps.

Bernie
 
Bernie is on the right track. The RDM Installation & User's Gudie has tons of information about configuring an environment to support PXE booting - especially to deploy BladeCenters. Even if you don't use RDM, the info is still valid. What specifically are you trying to do? It wasn't clear from your post how network booting is related to the problem you're having.
 
I haven't had much time to get much further on this project, but here is a link to what I've accomplished so far and I've included the text below. I've successfully booted to a win98 boot disk over the network using PXE boot. Cheezy, I know..but it's a start:)


PXE Boot Linux Implementation



Introduction
This document steps through the process of setting up a client/server pxe boot environment. I assume you know your way around a linux box, how to install software packages, edit configuration files and navigate your way through the filesystems. This configuration works for me but may not neccessarily work in your environment. This document is meant to be used as a guide.


Prerequisites
You need a server running your favorite distribution of linux. This example uses Fedora Core 2 by RedHat. The client can be any machine that has a nic capable of booting over the network.

On your linux server:
Install 'dhcpd' - Assigns client an ip address used for the PXE boot
Install 'tftpd' - Trivial ftp server. The client connects to this to download the image files.
Install 'syslinux' - Inlucdes the pxelinux and memdisk utilities

Copy 'memdisk' to /tftpboot


Setup your /etc/dhcpd.conf
allow booting;
option subnet-mask 255.255.255.0;

group {
next-server 192.168.168.12; #IP address of the tftp server
filename "pxelinux.0"; #PXE boot image filename located in /tftpboot
}

subnet 192.168.168.0 netmask 255.255.255.0 {
default-lease-time 600;
max-lease-time 7200;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.168.255;
option domain-name-servers 192.168.168.12;

#entry for dhcp server. dhcpd complains without it.
host client-1 {
hardware ethernet 00:02:B3:EE:F8:FC; #mac address of dhcpd server
fixed-address 192.168.168.12; #ip address of dhcp server
filename "/tftpboot/client01";
}

#The client you want to boot over the network
host client-2 {
hardware ethernet 00:09:6B:FF:15:DE;
fixed-address 192.168.168.101;
filename "pxelinux.0";
}
}



Setup your /tftpboot/pxelinux.cfg/default config file
default win98floppy
prompt 5

label local
LOCALBOOT 0

label win98floppy
kernel memdisk
append initrd=win.img


Build your first image file
As a proof of concept let us try to boot something simple like a Windows 98 boot floppy, but any boot floppy will do.
Put your boot floppy in the A: drive of your linux box and execute the following command to copy the contents of the floppy to the image file win.img.

dd if=/dev/fd0 of=/tftpboot/win.img bs=1024 count=1440

You can now remove the floppy.


Boot your client over the network
Make sure you have your client's nic configured to boot over the lan. Reboot your client. When prompted by the boot prompt type 'win98floppy'. You should see your client machine boot as if you had the 98 boot floppy in the A: drive.


Next...
The next thing I'd like to figure out is how to boot a larger OS such as Windows 2003 Server or Fedora for example. Obviously the entire OS will not fit into memory so we'll need to mount some kind of remote storage.

Please send questions or comments to klambert@earthmatrix.biz.




Kurin Lambert
klambert@earthmatrix.org
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top