source: branches/3.0/mindi/README.pxe @ 3168

Last change on this file since 3168 was 3168, checked in by Bruno Cornec, 7 years ago
  • Fix #697 by adding the iproute parameter at boot time to support addition of static routes
  • Property svn:keywords set to Id
File size: 5.1 KB
1$Id: README.pxe 3168 2013-07-26 06:50:01Z bruno $
3README for mondo/mindi usage with PXE
5mondorescue now supports the possibility to deploy mondo-images using the Pre eXecution Environment (PXE) standard.
6As this README only focusses on the mondorescue part, please read how to do Linux deployments with pxelinux on
8To use it, please do the following on your deployment server:
10Add the following line to your default file:
11label mondo
12        kernel vmlinuz-mondo
13        append initrd=initrd-mondo load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=131072 selinux=0 rw root=/dev/ram iso acpi=off apm=off devfs=nomount exec-shield=0 pxe [proto=nfs|sshfs|smbfs] [prefix=machine] [ipconf=(ipdev:ipadr:netmask:broadcast:gateway|ipdev:dhcp)] [hwaddr=M:A:C:A:D:R] [netfsmount=server:mountpoint] [netfsopt=-o option][netfspath=local_path] [ping=#] [iproute=-net:netdest:[netmask:Nm]gw:GW] ...
15ipdev is the device name (e.g. eth2)
16ipadr is the IP Address (e.g.
17netmask is the Netmask (e.g.
18broadcast is the Network broadcast (e.g.
19gateway is the default gateway (e.g.
20iproute is an additional static route using the route add syntax using : nstead of space to separate values
21dhcp is a keyword. Using it will provide all the previous 4 values to activate the LAN interface.
22hwaddr is the MAC address of the device you want to use to restore through
23proto is the protocol to use for mounting the remote share (default is NFS, sshfs and smbfs are also available)
24server is the ip addr of the Remote Network server
25mountpoint is the mount point on the Remote Network server to use (if NFS, should be in /etc/exports of the NFS server)
26netfsmount is the server and mountpoint on which the ISO is available, if different from the one at backup time. For SSHFS the server part can be of the form user@server.
27netfsopt may contains options passed to the mount command
28netfspath is the local path on the remote server where the image is located, if different from the one at backup time.
29local_path is the local directory under which the mage was made (with the -d option)
30ramdisk_size may have to be increase to 262144 or more on more recent distributions such as RHEL 6
31The [] mean this parameter is optional
32The () mean that you have a choice with the '|' meaning 'or'
34The initrd and kernel file come from the first bootable media
35created by mondoarchive. To get them, please issue:
37# mount /path/to/mondorescue-1.iso /mnt/cdrom -o loop
38# cp -a /mnt/cdrom/vmlinuz /var/tftpboot/vmlinuz-mondo
39# cp -a /mnt/cdrom/initrd.img /var/tftpboot/initrd-mondo
40# umount /mnt/cdrom
42Thus the PXE ROM will boot mondo's kernel and mondo's initrd in memory and will append all the right configuration options (as you find in isolinux.cfg on the first bootable media) to which you need to add the keyword pxe.
43(You need to have backup your data using the NFS option of mondoarchive)
45If you used the -p option of mondoarchive, you may specify the real name of mondo images to use during restore. To do that use prefix=machine on the initrd line, after the pxe keyword, to load the ISO images saved with -p machine.
46Without prefix keyword, the name of the images used during archiving with the -p option will be used (they may differ). If -p wasn't used then the name mondorescue-1.iso, ... will be used.
48During boot mondorestore will start your NFS configuration and mount mondo's content from the network rather than from a physical media. You may alter the IP configuration stored from the original machine by passing the ipconf option describing respectively the IP address, netmask, broadcast and default gateway you want to setup for the machine, separated by ':'. Or alternatively, you may specify the dhcp keyword so that a DHCP request is made to get those information. In the 2 cases, you have to mention on which physical interface those parameters should apply. On some configurations, you may also want to increase the number of ping queries made before the NFS mount, which is of 3 by default, using the ping option and give the number you want. If you have a different NFS server for the deployment than for the archiving, you can also precise it through the netfsmount option. The structure on both server under the mountpoint has to be the same.
50CAVEAT: the limit to the number of char on the append line is 255. Use symlinks to reduce the size of your path if needed.
52NOTE: If you don't have selinux=0 on the boot line, you may have issues restoring extended attributes on your filesystem and thus be unable to log on at next reboot after restore.
54Please report any problem around that tool to
562013-07-25 adds support for iproute
572011-10-09 adds support for hwaddr
582009-12-05 nfsopt added tp allow for custom options at mount time
592009-09-09 Changed to netfs for multi protocol support (nfs, sshfs, ...)
602009-05-07 nfspath added to allow redeployment from another NFS directory
612006-06-10 nfsmount added to allow redeployment from another NFS server
622006-06-02 ipdev added to allow redeployment on another interface
632005-12-18 new ipconf and ping option
642005-12-14 detailed explanations on where to find initrd and kernel
Note: See TracBrowser for help on using the repository browser.