Benutzer-Werkzeuge

Webseiten-Werkzeuge


installation_via_pxe

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen RevisionVorhergehende Überarbeitung
Nächste Überarbeitung
Vorhergehende Überarbeitung
installation_via_pxe [2011/06/22 13:45] admininstallation_via_pxe [2011/06/22 18:55] (aktuell) admin
Zeile 1: Zeile 1:
-=====PXE=====+===== PXE (Pre-eXecution Environment) =====
   *[[http://www.novell.com/coolsolutions/feature/19873.html|OES Installation Using PXE Boot and AutoYaST]]   *[[http://www.novell.com/coolsolutions/feature/19873.html|OES Installation Using PXE Boot and AutoYaST]]
   *[[http://opsamericas.com/?p=424|Configuring a TFTP/PXE Server]]   *[[http://opsamericas.com/?p=424|Configuring a TFTP/PXE Server]]
  
-  *DHCP-Server+==== DHCP-Server installieren und konfigurieren ====
 <file> <file>
 # dhcpd.conf # dhcpd.conf
-# 
-# Sample configuration file for ISC dhcpd 
-# 
- 
-# option definitions common to all supported networks... 
-option domain-name "example.org"; 
-option domain-name-servers ns1.example.org, ns2.example.org; 
- 
-default-lease-time 14400; 
-max-lease-time 7200; 
- 
-# if you do not use dynamical DNS updates: 
-# 
-# if you want to use dynamical DNS updates, you should first read 
-# read /usr/share/doc/packages/dhcp-server/DDNS-howto.txt 
-# 
-ddns-updates off; 
- 
-# Use this to enble / disable dynamic dns updates globally. 
-ddns-update-style none; 
- 
-# If this DHCP server is the official DHCP server for the local 
-# network, the authoritative directive should be uncommented. 
-#authoritative; 
- 
-# Use this to send dhcp log messages to a different log file (you also 
-# have to hack syslog.conf to complete the redirection). 
-log-facility local7; 
- 
-# 
-# Define RFC 3442 classless static route option (121); 
-# the following _example_ routes: 
-#    192.168.2.254/32 via 0.0.0.0     (device route) 
-#    192.168.2.253/32 via 192.168.1.2 (255.255.255.255) 
-#    192.2.0.128/25   via 192.168.1.2 (255.255.255.128) 
-#    192.168.2.0/24   via 192.168.1.2 (255.255.255.0) 
-#    172.16.0.0/12    via 192.168.1.2 (255.240.0.0) 
-#    10.0.0.0/      via 192.168.1.2 (255.0.0.0) 
-#    default          via 192.168.1.1 
-# have to be written as: 
-#    option rfc3442-classless-static-routes 
-#           32,  192, 168, 2, 254,    0,   0, 0, 0, 
-#           32,  192, 168, 2, 253,  192, 168, 1, 2, 
-#           25,  192,   2, 0, 128,  192, 168, 1, 2, 
-#           24,  192, 168, 3,       192, 168, 1, 2, 
-#           12,  172, 16,           192, 168, 1, 2, 
-#            8,   10,               192, 168, 1, 2, 
-#            0,                     192, 168, 1, 1; 
-# 
-# Note: you have to specify the default gateway here 
-# as well, because when classless routes are in use, 
-# the 'routers' option is ignored by the dhcp client. 
-# 
-option rfc3442-classless-static-routes code 121 = array of unsigned integer 8; 
- 
  
 # No service will be given on this subnet, but declaring it helps the  # No service will be given on this subnet, but declaring it helps the 
Zeile 72: Zeile 17:
 range 192.168.2.10 192.168.2.42; range 192.168.2.10 192.168.2.42;
 } }
-# Hosts which require special configuration options can be listed in 
-# host statements.   If no address is specified, the address will be 
-# allocated dynamically (if possible), but the host-specific information 
-# will still come from the host declaration. 
- 
-host passacaglia { 
-  hardware ethernet 0:0:c0:5d:bd:95; 
-  filename "vmunix.passacaglia"; 
-  server-name "toccata.fugue.com"; 
-} 
- 
-# Fixed IP addresses can also be specified for hosts.   These addresses 
-# should not also be listed as being available for dynamic assignment. 
-# Hosts for which fixed IP addresses have been specified can boot using 
-# BOOTP or DHCP.   Hosts for which no fixed address is specified can only 
-# be booted with DHCP, unless there is an address range on the subnet 
-# to which a BOOTP client is connected which has the dynamic-bootp flag 
-# set. 
-host fantasia { 
-  hardware ethernet 08:00:07:26:c0:a5; 
-  fixed-address fantasia.fugue.com; 
-} 
- 
-# You can declare a class of clients and then do address allocation 
-# based on that.   The example below shows a case where all clients 
-# in a certain class get addresses on the 10.17.224/24 subnet, and all 
-# other clients get addresses on the 10.0.29/24 subnet. 
- 
-class "foo" { 
-  match if substring (option vendor-class-identifier, 0, 4) = "SUNW"; 
-} 
- 
-shared-network 224-29 { 
-  subnet 10.17.224.0 netmask 255.255.255.0 { 
-    option routers rtr-224.example.org; 
-  } 
-  subnet 10.0.29.0 netmask 255.255.255.0 { 
-    option routers rtr-29.example.org; 
-  } 
-  pool { 
-    allow members of "foo"; 
-    range 10.17.224.10 10.17.224.250; 
-  } 
-  pool { 
-    deny members of "foo"; 
-    range 10.0.29.10 10.0.29.230; 
-  } 
-} 
- 
 </file> </file>
  
Zeile 127: Zeile 23:
  DHCPD_INTERFACE="eth0"  DHCPD_INTERFACE="eth0"
 </file> </file>
-  *ATFTP-Server 
-  /etc/sysconfig/atftpd 
-   
-  ATFTPD_OPTIONS="--daemon --no-multicast" 
  
-  *HTTP oder FTP oder SAMBA oder NFS Server+==== ATFTP-Server installieren und konfigurieren ==== 
 + 
 +  *zypper in atftp 
 +  */etc/sysconfig/atftpd 
 +    *ATFTPD_OPTIONS="--daemon --no-multicast"
  
-/etc/dhcpd.conf (auf Plank) +  * Gesamten CD- oder DVD-Inhalt nach /pxeboot/dvd_name kopieren 
-  filename "pxelinux.0"; +  */pxeboot/pxelinux.cfg/default 
-  next-server 192.168.100.4; +
-   +
-vi default+
  
 <file> <file>
installation_via_pxe.1308743100.txt.gz · Zuletzt geändert: von admin