Changes between Version 30 and Version 31 of PxeUsage
- Timestamp:
- 10/29/10 09:10:11 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PxeUsage
v30 v31 12 12 13 13 14 == Systemimager activation ==14 == Systemimager pr Sali activation == 15 15 16 16 To activate this on a client depends on your version of systemimager and your preferred method 17 17 18 === Telnet method ===18 === Systemimager telnet method === 19 19 20 20 To activate this on a client you must add the following line to the ''systemimager master'' script of the node. It will remove the pxe config file for the node from the pxe bootserver. I personally place the line just before the ''umount'' commands. See below which command to use for which systemimager version. … … 31 31 === Post install script method === 32 32 33 With systemimager version 3.7 and higher it easier tosetup. In the systemimager server examples directory there is an pxeconfig post installation script (Author: Ole Holm Nielsen), eg:33 With systemimager version 3.7 and higher and [https://subtrac.sara.nl/oss/sali Sali] there is an easier setup. In the systemimager server examples directory there is an pxeconfig post installation script (Author: Ole Holm Nielsen), eg: 34 34 {{{ 35 35 cp /usr/share/doc/systemimager-server/examples/post-install/30all.pxeconfig \\ … … 39 39 == Example how to use pxeconfig utility == 40 40 41 The pxeconfig command creates soft-links in the ''/tftpboot/pxelinux.cfg'' directory named as the hexadecimally encoded IP-address of the clients, and these links will point to one of the files default.*. As designed, the PXE network booting process will download the file given by the hexadecimal IP-address, and hence network installation of the node will take place. With pxeconfig you can easily create those links for the host(s) 41 The pxeconfig command creates soft-links in the ''/tftpboot/pxelinux.cfg'' directory named as: 42 * hexadecimally encoded IP-address of the clients 43 * mac address with a ''01-'' prefix 42 44 43 There are serveral ways to run pxeconfig: 44 * interactively, network range 45 * hostname(s) 46 * host range 47 * rack(x) and node(y) specification 45 The links will point to one of the files default.*. As designed, the PXE network booting process will download the file given by the hexadecimal IP-address 46 or 01-<mac address>, and hence network installation of the node will take place. With pxeconfig you can easily create those links for the host(s) 48 47 49 We will discuss the ''long'' options for pxeconfig for the ''short'' options: 48 For usage and some examples 50 49 {{{ 51 pxeconfig -h50 pxeconfig [-f,--filename <name>] <hosts> 52 51 }}} 53 52 54 if {{{-f,--filename}}} is not specified the program will display a menu w here the user can choose from.53 if {{{-f,--filename}}} is not specified the program will display a menu with pxe configuration files where the user can choose from. 55 54 56 === host name(s) ===55 === hosts specifications == 57 56 58 the following command will make links to the ''default.node_install'' file for hosts ''gb-r1n1'' and ''gb-r1n2'': 57 With ''[]'' you can specify a range. This ranges are not only limited to numbers. Some examples 58 59 * The first five nodes of rack 16 59 60 {{{ 60 pxeconfig gb-r1n1 gb-r2n1 --filename default.node_install 61 gb-r16n[1-5] 61 62 }}} 62 63 63 === host range === 64 * The first five nodes and node 12 and 18 of rack 16 to 20 65 {{{ 66 gb-r[16-20]n[1-5,12,18] 67 }}} 64 68 65 We want to make links for a ''range'' of hosts, eg node1 till node100, This can be acomplished with these commands: 66 * {{{ pxeconfig --basename node --host-range 1-100 --filename default.node_install}}} 67 * {{{ pxeconfig --basename node --start 1 --end 100 }}} 69 * The first five nodes de in rack 16 with padding enabled 70 {{{ 71 gb-r[16]n[01-5] 72 }}} 68 73 69 74 70 Some sites have name their hosts, eg: node001 till node099. This can also be acomplished in several ways: 71 * {{{ pxeconfig --basename node --equal-width --host-range 1-099 }}} 72 * {{{ pxeconfig --basename node --host-range 001-099 }}} 73 * {{{ pxeconfig --basename node --start 001 --end 099 }}} 74 75 === rack(x) and node(y) specification === 76 77 We want make links for hosts with a naming schema(s) like this: 75 === Example === 76 * the following command will make links to the ''default.node_install'' file for hosts in rack 2 and host bas. Where bas is 77 defined in ''pxeconfig.conf'' as host with a mac address 78 78 {{{ 79 gb-r<number>n<number> 80 node-(number)-(number) 79 pxeconfig gb-r2n[1-20] bas --filename default.node_install 81 80 }}} 82 83 These examples will create links for node1, node2 and node3 in rack1, rack2 and rack3:84 * {{{ pxeconfig --basename gb- -rack r1-r3 --node n1-n3 --filename default.memtest }}}85 * {{{ pxeconfig --basename node --rack 1-3 --node 1-3 --filename default.memtest }}}86 87 When leading zeros are used, then rack and/or node names will be padded with zeros, eg:88 * {{{ pxeconfig --basename gb- -rack r01-r02 --node n01-n02 --filename default.memtest }}}89 {{{90 will create links for hosts:91 * gb-r01n0192 * gb-r01n0293 * gb-r02n0194 * gb-r02n0295 }}}