Linux network installation and automation installation __linux

Preliminary Knowledge Software Requirements Hardware Requirements System Process Manual Installation Action steps Automating the installation of Linux FAQ

Preliminary Knowledge PXE

PXE (preboot eXecution Environment) is a protocol designed by Intel to enable the computer to boot over the network. The protocol is divided into client and server ends, PXE client in the network card ROM, when the computer boot, the BIOS to the PXE client into memory execution, and display the Command menu, after the user selection, PXE client will be placed in the remote operating system through The network downloads to run locally. DHCP

DHCP (Dynamic Host Configuration Protocol, dynamically hosted Configuration Protocol) TFTP

TFTP (Trivial file Transfer Protocol, simple Files Transfer Protocol) Network install Linux

The installation media is located on the network, different from the disc installation and local Disk mode. Common network installation methods are NFS image, FTP, HTTP, and so on. The following figure:

Kickstart Unattended Installation

Supported from a version of RHEL, the main purpose is to reduce the human-computer interaction during installation and improve installation efficiency.

Using this method, you can simply define a configuration file (usually on the installation server), which the installer reads from the file and installs it automatically.

Examples see Linux/root/anaconda-ks.cfg files

Software Requirements

The following software, in addition to PXE, can be found in the RHRL5 release CD image.
You can use the Yum installation. Such as:

# yum Install DHCP PXE

PXE DHCP

DHCP TFTP

Tftp-server

TFTP (client, not required, verification of tftp-server and convenience points for debugging) Syslinux

Syslinux (the installation process needs to use the file named pxelinux.0) Pykickstat, System-config-kickstart

These two software are not required, but System-config-kickstart relies on Pykickstat a Linux distribution

Theoretically all Linux distributions can be installed in this way, and nuances should be found in each release's manual. NFS, FTP, HTTP

At least one of the software must be installed, or you will not be able to install the network.

Hardware Requirements Client

With PXE support, you can start the server from the network

No special requirements

Network

Switch--the client and server are connected to a switch and can accept each other's broadcast packets

System Process as shown in figure

The client's BIOS is set to boot from the network

Client obtains IP address from DHCP server

Client-specified TFTP load boot mirror from DHCP server

Automate the installation based on the configuration file in the TFTP server. If the profile gives too little information, it will go into the interactive installation mode. In interactive installation mode, you can choose where to install the media on the network and how to access it.
Manual Installation Action steps preparing to install media

M Ount CD image file

# mkdir-p/media/owlinux36

# mount-t Iso9660/root/owlinux-3.6-u1.iso/media/owlinux36-o Loop

Verify that the mount is successful

# cd/media/owlinux36 && ls

Configure the TFTP server and verify

Edit configuration file

# vi/etc/xinetd.d/tftp

# Default:off # description:the TFTP server serves files using the Trivial file transfer/ # protocol. The TFTP protocol is often used to boot diskless/ # workstations, download configuration files to network-aware printers,/ # and to-start the installation process for some operating systems. Service TFTP { Disable = no Socket_type = Dgram protocol = UDP Wait = yes user = root Server =/USR/SBIN/IN.TFTPD Server_args =-s/tftpboot Per_source = 11 CPS = 100 2 Flags = IPV4 }

Start the TFTP service

# Chkconfig TFTP on

# service xinetd re start

Verifying the TFTP service

See if TFTP is listening on the network

# netstat--listen | grep tftp

Run the TFTP command in Linux or Windows command line mode and download the files in/tftpboot to test the TFTP service for normal.

# Create a new file in/tftpboot
# Touch/tftpboot/file4test

# Linux under command
# tftp 192.168.95.1-c get file4test

# Command under Windows

# tftp 192.168.95.1 get file4test

Configure the DHCP server and verify

Edit configuration file

# vi/etc/dhcpd.conf

Add a red configuration item

To modify a red and blue configuration item

Comment Out yellow configuration items (in automatic installation