CN109783082B

CN109783082B - Erection method of UEFI Http boot server

Info

Publication number: CN109783082B
Application number: CN201910002702.6A
Authority: CN
Inventors: 刘浩君
Original assignee: Zhengzhou Yunhai Information Technology Co Ltd
Current assignee: Zhengzhou Yunhai Information Technology Co Ltd
Priority date: 2019-01-02
Filing date: 2019-01-02
Publication date: 2022-02-18
Anticipated expiration: 2039-01-02
Also published as: CN109783082A

Abstract

According to the erection method of the UEFI Http Boot server, under a Linux system, the erection of the server is completed by executing a system command according to the erection method, whether the IPV4 or IPV6 function of the UEFI Http Boot of a product can meet the customer requirement can be tested, and the quality of the product is improved.

Description

Erection method of UEFI Http boot server

Technical Field

The invention relates to the field of computer services, in particular to an erection method of a UEFI Http boot server.

Background

UEFI, known as a "Unified Extensible fixed Interface" (Unified Extensible Firmware Interface), is a standard for describing completely new types of interfaces in detail. The interface is used for loading the operating system from the pre-started operating environment to the operating system automatically, so that the starting program is simplified, and the time is saved. UEFI will provide a clear specification of the interface between the operating system and the software platform that is fixed in hardware that is enabled at boot-up, and will support a computer architecture independent means for initializing plug-in cards.

Currently, the mainstream system starting modes are UEFI boot, but the requirements of clients on the network booting mode are different according to different requirements, and some clients require IPV4 booting of UEFI PXE; some customer requirements are the Boot of IPV4 or IPV6 of the Http Boot. In order to realize the functions of the UEFI Http boot, a UEFI Http boot server needs to be erected in the system.

Disclosure of Invention

In view of the above problems, the present invention is directed to a method for erecting a UEFI Http boot server.

In order to achieve the purpose, the invention is realized by the following technical scheme: a method for erecting a UEFI Http boot server comprises the following steps:

step 1: installing services, tools and software packages for network configuration under a Linux system;

step 2: setting an IP address, a gateway and a DNS;

and step 3: setting DHCP4 and DHCP 6;

and 4, step 4: establishing and setting a lease authority of DHCP;

and 5: setting and editing DNS, HTTP and RADDD;

step 6: opening IPv6routing, and setting automatic starting without starting;

and 7: starting IPv6routing and checking whether the starting is successful;

and 8: modifying DHCP server and sending out IP through network card;

and step 9: connecting the network cable, and restarting all the servers.

Further, the step 1 specifically comprises:

installing a DHCP and executing a command of sudo apt-get install isc-DHCP-server;

installing a DNS and executing a command of sudo apt-get install bind9 sudo apt-get install dnsumils;

installing HTTP, and executing a command Sudo apt-get install apache 2;

and (4) installing the radvd and executing a command sudo apt-get install radvd.

Further, the step 3 specifically comprises:

modifying dhcpd.conf by operating an instruction sudo nano/etc/dhcp/dhcpd.conf;

and modifying dhcpd6.conf by operating the instruction sudo nano/etc/dhcp/dhcpd6. conf.

Further, step 3 further comprises: if there is no dhcpd6.conf, it can be modified by copying dhcp.conf.

Further, in step 5, the setting of the DNS mainly includes:

newly adding zones, newly adding contents IPV4 and IPV6 in named.conf;

local is replicated and renamed db.cloudboot.com and db.cloudboot.6.com;

editing db.cloudboot.com under the IPV 4;

edit db.

Further, in step 5, the setting of HTTP mainly includes:

modify 000-default, folder path, and apache2. conf;

establishing an EFI folder;

the startup file is copied efi and moved to the original directory of files.

Further, the step 8 further includes: find INTERFACE and modify to INTELFACE ═ eth0 "< -eth 0.

Further, the step 9 specifically includes: connecting the network cable, and restarting DHCP, DNS, apache2 and radvd in sequence.

Compared with the prior art, the invention has the beneficial effects that: according to the erection method of the UEFI Http Boot server, under a Linux system, the erection of the server is completed by executing a system command according to the erection method, whether the IPV4 or IPV6 function of the UEFI Http Boot of a product can meet the customer requirement can be tested, and the quality of the product is improved.

The invention is based on a Linux system, has strong universality and wide application; the system environment stability of the follow-up test is ensured, and the test conclusion is real and reliable.

Therefore, compared with the prior art, the invention has prominent substantive features and remarkable progress, and the beneficial effects of the implementation are also obvious.

Drawings

FIG. 1 is a flow chart of the method of the present invention.

Fig. 2 is a network setup diagram of the present invention.

Detailed Description

The following description of the embodiments of the present invention will be made with reference to the accompanying drawings.

As shown in fig. 1, the erection method of the UEFI Http boot server includes the following steps:

step 1: and installing services, tools and software packages for network configuration under the Linux system. The method specifically comprises the following steps:

installing HTTP, and executing a command Sudo apt-get install apache 2;

Step 2: setting an IP address, a gateway and a DNS.

And step 3: DHCP4 and DHCP6 are set. The method specifically comprises the following steps:

modifying dhcpd.conf by operating an instruction sudo nano/etc/dhcp/dhcpd.conf;

If there is no dhcpd6.conf, it can be modified by copying dhcp.conf.

And 4, step 4: and establishing and setting the lease authority of the DHCP.

And 5: DNS, HTTP and RADVD are set and edited.

The setting of the DNS mainly includes:

newly adding zones, newly adding contents IPV4 and IPV6 in named.conf;

local is replicated and renamed db.cloudboot.com and db.cloudboot.6.com;

editing db.cloudboot.com under the IPV 4;

edit db.

The setting of HTTP mainly includes:

modify 000-default, folder path, and apache2. conf;

establishing an EFI folder;

the startup file is copied efi and moved to the original directory of files.

Step 6: and opening the IPv6routing and setting the automatic starting without starting.

And 7: IPv6routing is started and it is checked whether the start was successful.

And 8: and modifying the DHCP server and sending out the IP through the network card.

Find INTERFACE and modify to INTELFACE ═ eth0 "< -eth 0.

And step 9: connecting the network cable, and restarting all the servers.

The method specifically comprises the following steps: connecting the network cable, and restarting DHCP, DNS, apache2 and radvd in sequence.

On the basis, the specific implementation process is as follows:

1) installing required application under Linux system

a. Installing DHCP execution command sudo apt-get install isc-DHCP-server

b. Installing DNS execution command sudo apt-get install bind9 sudo apt-get install dnsutils

c. Install http execute command Sudo apt-get install apache2

RADDD (Optional) execution command sudo apt-get install radvd

2) IP addresses, gateways, DNS, etc. are set as shown in fig. 2.

3) Setting DHCP4:

conf, sudo nano/etc/dhcp/dhcpd. conf

Modified (starting from default-release-time 600; ", add the following contents):

default-lease-time 600；max-lease-time 7200；allow booting；

option domain-name"cloudboot.com"；option domain-name-servers192.168.184.1；option vendor-class-identifier"HTTPClient"；

option bootfile-name"http://www.cloudboot.com/EFI/RU.efi"；

subnet 192.168.184.0netmask 255.255.255.0{range192.168.184.5192.168.184.253；}

setting DHCP6:

modify dhcpd6.conf, instruction:

sudo nano/etc/dhcp/dhcpd6.conf

note if there is no dhcpd6.conf, dhcp. conf can be copied to modify

sudo cp dhcpd.conf dhcpd6.conf

Modified (starting with default-release-time 600; add the following):

default-lease-time 600；

max-lease-time 7200；

allow booting；

log-facility local7；

option dhcp6.vendor-class code 16＝{integer 32,integer 16,string}；option dhcp6.rfc5970-bootfile-url code 59＝string；

subnet6 2001:db8:0:1::/64{range6 2001:db8:0:1::1292001:db8:0:1::254；option dhcp6.domain-search"cloudbootip6.com"；option dhcp6.name-servers 2001:db8:0:1::1；option dhcp6.vendor-class 00"HTTPClient"；option dhcp6.rfc5970-bootfile-url"http://www.cloudbootip6.com/EFI/RU.efi"；}

4) establishing and setting the lease authority of the DHCP, and commanding the following steps:

sudo touch/var/lib/dhcp/dhcpd6.leases

sudo chmod 666/var/lib/dhcp/dhcpd6.leases

5) setting DNS:

connf add zones, the following instructions:

sudo nano/etc/bind/named.conf

newly added content IPV4:

zone"cloudboot.com"{type master；file"/etc/bind/db.cloudboot.com"；}；

newly added content IPV6:

zone"cloudbootip6.com"{type master；file"/etc/bind/db.cloudbootip6.com"；}；

local is replicated and is renamed to db.

The following instructions:

cd/etc/bind/

sudo cp db.local db.cloudboot.com sudo cp db.local

db.cloudbootip6.com

compile db, cloudboot, com under IPV4, order:

nano db.cloudboot.com

the modification is as follows:

compile db, cluudbook 6.com under IPV6, order:

sudo nano db.cloudbootip6.com

the modification is as follows:

6) setting Http (apache2)

Modify 000-default, instruction:

sudo nano/etc/apache2/sites-available/000-default.conf

modify the folder path to remove the following html leaves/var/www-

Modify Apache2.conf (Servername may appear when Apache server starts up, the following string may be added:

sudo nano/etc/apache2/apache2.conf

join in any line ServerName localhost

Establishing an EFI folder, and ordering:

sudo mkdir/var/www/EFI

copy the efi file for the opener, move to the original directory of files and order:

cp<file name>/var/www/EFI/<file name>

if the file or file name used is not Shell, the files dhcpd. conf and dhcpd6.conf are modified as follows (at file name)

option bootfile-name"http://www.cloudboot.com/EFI/<file name>"；

7) Establish radvd settings and edit it

sudo touch tc/radvd.conf sudo

nano/etc/radvd.conf

8) Write the following information into the radvd. conf (Note: eth0 is the name of the network card, it is consistent with the name in the system)

9) Opening IPv6routing, setting automatic starting of starting

sudo nano/etc/sysctl.conf

(removing the # font size before the following string)

net.ipv6.conf.all.forwarding＝1

10) IPv6routing is started immediately and checked for success

sudo sysctl-p

(show:net.ipv6.conf.all.forwarding＝1)

11) Modifying DHCP server to send out IP through the network card

sudo nano/etc/default/isc-dhcp-server

Finding INTERFACE, and modifying to INTELFACE ═ eth0 [ -eth0, which is the network card name identified under OS

12) Connecting a network cable, restarting all the servers:

a. restarting DHCP

service isc-dhcp-server restart(ipv4)

service isc-dhcp-server6restart(ipv6)

b. Restarting DNS

service bind9restart

c. Restart apache2

service apache2restart

d. Restarting radvd

sudo/etc/init.d/radvd restart

Thus, the server capable of being UEFI Http boot is erected.

The server is erected, whether the IPV4 or the IPV6 function of UEFI Http Boot of a product can meet the customer requirements can be tested, and the quality of the product is improved.

The invention is further described with reference to the accompanying drawings and specific embodiments. It should be understood that these examples are for illustrative purposes only and are not intended to limit the scope of the present invention. Further, it should be understood that various changes or modifications of the present invention may be made by those skilled in the art after reading the teaching of the present invention, and these equivalents also fall within the scope of the present application.

Claims

1. A method for erecting a UEFI Http boot server is characterized by comprising the following steps:

step 2: setting an IP address, a gateway and a DNS;

and step 3: setting DHCP4 and DHCP 6;

and 4, step 4: establishing and setting a lease authority of DHCP;

and 5: setting and editing DNS, HTTP and RADDD;

step 6: opening IPv6routing, and setting automatic starting without starting;

and 7: starting IPv6routing and checking whether the starting is successful;

and 8: modifying DHCP server and sending out IP through network card;

and step 9: connecting a network cable, and restarting all the servers;

the step 3 specifically comprises the following steps:

modifying dhcpd.conf by operating an instruction sudo nano/etc/dhcp/dhcpd.conf;

modifying dhcpd6.conf by executing the instruction sudo nano/etc/dhcp/dhcpd6. conf;

in step 5, the setting of the DNS mainly includes:

newly adding zones, newly adding contents IPV4 and IPV6 in named.conf;

local is replicated and renamed db.cloudboot.com and db.cloudboot.6.com;

editing db.cloudboot.com under the IPV 4;

editing db.

In step 5, the setting of HTTP mainly includes:

modify 000-default, folder path, and apache2. conf;

establishing an EFI folder;

the startup file is copied efi and moved to the original directory of files.

2. The UEFI Http boot server erection method according to claim 1, wherein the step 1 specifically comprises:

installing a DNS and executing a command of sudo apt-get install bind9 sudo apt-get install sessions;

installing HTTP, and executing a command Sudo apt-get install apache 2;

3. The UEFI Http boot server erection method according to claim 1, wherein the step 3 further comprises: if there is no dhcpd6.conf, it can be modified by copying dhcp.conf.

4. The UEFI Http boot server erection method according to claim 1, wherein the step 8 further comprises: find INTERFACE and modify to INTELFACE = "eth 0" < -eth 0.

5. The UEFI Http boot server erection method according to claim 1, wherein the step 9 specifically is: connecting the network cable, and restarting DHCP, DNS, apache2 and radvd in sequence.