Server starting control method, device and equipment and storage medium

Abstract

The invention discloses a server starting control method, device and equipment and a storage medium, and the method comprises the steps: controlling the starting of a server, and detecting network card equipment in the starting process of the server; judging whether a PXE control closing request corresponding to the network card equipment exists or not; wherein the PXE closing control request corresponding to the network card equipment comprises a target protocol identifier corresponding to a target slot position where the network card equipment is located; and if yes, deleting the PXE starting address in the starting read-only memory of the network card equipment, and controlling the server to continue to start. According to the invention, PXE starting control of the network card equipment corresponding to any slot position is realized.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and more specifically, to a server startup control method, device, equipment and storage medium. Background Art

[0002] In large-scale server deployment scenarios, administrators use IPMI (Intelligent Platform Management Interface) to set all target servers to PXE (Preboot Execution Environment) boot, and then automatically download and install the operating system through the network, greatly improving deployment efficiency. When a server fails and on-site access is limited, administrators can use IPMI to set the server to PXE boot, boot to the diagnostic or recovery environment, and perform remote troubleshooting and repairs. However, for PXE with multiple network cards, the relevant technology cannot implement PXE boot control of network card devices corresponding to any slot.

[0003] Therefore, how to implement PXE startup control of a network card device corresponding to any slot is a technical problem that those skilled in the art need to solve. Summary of the invention

[0004] The purpose of the present application is to provide a server startup control method, device, equipment and storage medium, which realize PXE startup control of a network card device corresponding to any slot.

[0005] To achieve the above object, the present application provides a server startup control method, comprising:

[0006] Controlling the server startup and detecting the network card device during the startup process of the server;

[0007] Determine whether there is a PXE shutdown control request corresponding to the network card device; wherein the PXE shutdown control request corresponding to the network card device includes a target protocol identifier corresponding to the target slot where the network card device is located;

[0008] If it exists, the PXE boot address in the boot read-only memory of the network card device is deleted, and the server is controlled to continue booting.

[0009] Wherein, detecting the network card device during the startup process of the server includes:

[0010] Scanning a startup device during the startup process of the server;

[0011] If a network card device is scanned, the process proceeds to the step of determining whether there is a PXE control shutdown request corresponding to the network card device.

[0012] Before determining whether there is a PXE control shutdown request corresponding to the network card device, the method further includes:

[0013] Determine whether the network card device has a startup read-only memory;

[0014] If yes, the process proceeds to the step of determining whether there is a PXE control shutdown request corresponding to the network card device.

[0015] Wherein, judging whether there is a PXE control shutdown request corresponding to the network card device includes:

[0016] Determine whether there is a PXE control request corresponding to the network card device; wherein the PXE control request includes a target protocol identifier and a PXE startup state corresponding to the target slot where the network card device is located, and the PXE startup state includes an on state and a off state;

[0017] If there is a PXE control request corresponding to the network card device, determining whether the PXE startup state in the PXE control request is a closed state;

[0018] If the PXE startup state in the PXE control request is a shutdown state, it is determined that there is a shutdown PXE control request corresponding to the network card device.

[0019] The PXE control request further includes an effectiveness type, and the effectiveness type includes a one-time effectiveness and a permanent effectiveness.

[0020] Among them, it also includes:

[0021] The PXE shutdown control request corresponding to the network card device is received through the intelligent platform management interface.

[0022] Wherein, before deleting the PXE boot address in the boot read-only memory of the network card device and controlling the server to continue booting, the method further includes:

[0023] Obtaining a target correspondence relationship; wherein the target correspondence relationship is used to record the correspondence between the slot, the protocol identifier, the slot identifier, and the bus address range;

[0024] Correspondingly, deleting the PXE boot address in the boot read-only memory of the network card device and controlling the server to continue booting includes:

[0025] Determine a corresponding target slot according to the target protocol identifier in the PXE shutdown control request, and determine a corresponding target slot identifier and a target bus address range in the target corresponding relationship according to the target slot;

[0026] Obtaining slot identifiers of all boot devices through a peripheral component interconnection standard protocol, and determining whether the target slot identifier exists;

[0027] If it does not exist, control the server to continue starting;

[0028] If it exists, determining that the boot device whose slot identifier is the target slot identifier is the network card device;

[0029] Read the target bus address of the network card device through the input and output ports, and determine whether the target bus address is within the target bus address range;

[0030] If yes, then deleting the PXE boot address in the boot read-only memory of the network card device, and controlling the server to continue booting;

[0031] If not, the server is controlled to continue starting.

[0032] To achieve the above object, the present application provides a server startup control device, comprising:

[0033] A detection module, used for controlling the startup of the server and detecting the network card device during the startup process of the server;

[0034] The first judgment module is used to judge whether there is a PXE control request corresponding to the network card device; if so, the work flow of the deletion module is started; wherein the PXE control request corresponding to the network card device includes a target protocol identifier corresponding to the target slot where the network card device is located;

[0035] The deletion module is used to delete the PXE startup address in the startup read-only memory of the network card device and control the server to continue to start.

[0036] To achieve the above objectives, the present application provides an electronic device, including:

[0037] Memory for storing computer programs;

[0038] A processor is used to implement the steps of the above-mentioned server startup control method when executing the computer program.

[0039] To achieve the above-mentioned purpose, the present application provides a non-volatile storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above-mentioned server startup control method are implemented.

[0040] To achieve the above-mentioned purpose, the present application provides a computer program product, including a computer program, which implements the steps of the above-mentioned server startup control method when executed by a processor.

[0041] It can be seen from the above scheme that a server startup control method provided by the present application includes: controlling server startup, detecting a network card device during the startup process of the server; judging whether there is a PXE shutdown control request corresponding to the network card device; wherein the PXE shutdown control request corresponding to the network card device includes a target protocol identifier corresponding to the target slot where the network card device is located; if so, deleting the PXE startup address in the startup read-only memory of the network card device, and controlling the server to continue startup.

[0042] The server startup control method provided by the present application pre-sets the corresponding relationship between the slot and the protocol identifier. By default, each network card device enables PXE startup. When the user needs to turn off the PXE startup function of the network card device corresponding to the target slot, a PXE shutdown control request is constructed according to the target protocol identifier corresponding to the target slot. According to the PXE shutdown control request, the PXE startup address in the startup read-only memory of the network card device is deleted, so that the network card device cannot realize PXE startup, and the PXE startup function is turned off. It can be seen that the present application realizes the PXE startup control of the network card device corresponding to any slot. The present application also discloses a server startup control device, an electronic device, a non-volatile storage medium and a computer program product, which can also achieve the above-mentioned technical effects.

[0043] It should be understood that the foregoing general description and the following detailed description are exemplary only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following is a brief introduction to the drawings required for use in the embodiments or the prior art descriptions. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. The drawings are used to provide a further understanding of the present disclosure and constitute a part of the specification. Together with the following specific implementation methods, they are used to explain the present disclosure, but do not constitute a limitation to the present disclosure. In the drawings:

[0045] Figure 1 is a flow chart of a server startup control method according to an exemplary embodiment;

[0046] Figure 2 is a flow chart of another server startup control method according to an exemplary embodiment;

[0047] Figure 3 is a structural diagram of a server startup control device according to an exemplary embodiment;

[0048] Figure 4 The figure is a structural diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0049] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application. In addition, in the embodiments of the present application, "first", "second", etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0050] The embodiment of the present application discloses a server startup control method, which implements PXE startup control of a network card device corresponding to any slot.

[0051] See also Figure 1 , according to an exemplary embodiment, a flow chart of a server startup control method is shown, such as Figure 1 As shown, including:

[0052] S101: Control the server to start up, and detect the network card device during the startup process of the server;

[0053] In this step, after the server is started, the network card device is detected. If the network card device is detected, the process proceeds to S102, otherwise the server is started continuously.

[0054] As a feasible implementation, detecting the network card device during the startup process of the server includes: scanning the startup device during the startup process of the server; if the network card device is scanned, entering the step of determining whether there is a PXE control request corresponding to the network card device.

[0055] In a specific implementation, after the server is started, the startup device is scanned, including a hard disk, a network card device, a CD (Compact Disc), a USB flash drive (USB Flash Drive), etc. If a network card device is detected, enter S102, otherwise continue to start the server.

[0056] S102: Determine whether there is a PXE shutdown control request corresponding to the network card device; if yes, proceed to S103; wherein the PXE shutdown control request corresponding to the network card device includes a target protocol identifier corresponding to the target slot where the network card device is located;

[0057] In a specific implementation, the corresponding relationship between the slot and the protocol identifier is preset. By default, each network card device enables PXE booting. When a user needs to turn off the PXE booting function of the network card device corresponding to the target slot, a PXE turn-off control request is constructed according to the target protocol identifier corresponding to the target slot, and sent to the server through the intelligent platform management interface. That is, as a feasible implementation method, this embodiment also includes: receiving the PXE turn-off control request corresponding to the network card device through the intelligent platform management interface.

[0058] In this step, when the server scans the network card device, it determines the target slot where the network card device is located, and determines the target protocol identifier corresponding to the target slot according to the preset corresponding relationship between the slot and the protocol identifier. It is determined whether there is a PXE shutdown control request containing the target protocol identifier, that is, it is determined whether there is a PXE shutdown control request corresponding to the network card device, if so, it enters S103, otherwise it continues to start the server.

[0059] As a preferred implementation, before determining whether there is a PXE control request corresponding to the network card device, it also includes: determining whether there is a boot read-only memory for the network card device; if so, entering the step of determining whether there is a PXE control request corresponding to the network card device.

[0060] It is understandable that after the server detects the network card device, it will hand over the control to the BootROM (Boot Read-Only Memory) of the network card device. The code in the BootROM will first perform a self-test to ensure that the network interface and PXE boot function are normal. Therefore, after the server detects the network card device, it first determines whether the network card device has a boot read-only memory, which can be determined by the 0x55AA flag bit of the BootROM firmware. If there is a boot read-only memory, it means that the PXE boot function is turned on. At this time, it continues to determine whether there is a PXE control request corresponding to the network card device. If there is no boot read-only memory, it means that the PXE boot function cannot be implemented, and the server continues to start.

[0061] As a feasible implementation method, determining whether there is a PXE control request corresponding to the network card device includes: determining whether there is a PXE control request corresponding to the network card device; wherein the PXE control request includes a target protocol identifier and a PXE startup status corresponding to a target slot where the network card device is located, and the PXE startup status includes an on status and a off status; if there is a PXE control request corresponding to the network card device, determining whether the PXE startup status in the PXE control request is a off status; if the PXE startup status in the PXE control request is a off status, determining that there is a PXE control request corresponding to the network card device.

[0062] In the specific implementation, it is first determined whether there is a PXE control request corresponding to the network card device. If so, the PXE startup status is read. If the PXE startup status is closed, it is determined that there is a PXE control request corresponding to the network card device. If the PXE startup status is open, it is determined that there is no PXE control request corresponding to the network card device.

[0063] As a preferred implementation, the PXE control request also includes an effectiveness type, which includes a one-time effectiveness and a permanent effectiveness. For example, the PXE control request may be "ipmi raw 0x3c 0x36 xxx xx x", where xxx is a protocol identifier, xx is a PXE startup state, and x is an effectiveness type.

[0064] It should be noted that for a one-time effective PXE control request, after the server is started, the PXE control request is deleted to prevent the PXE control request from taking effect again the next time the server is started. For a permanently effective PXE control request, after the server is started, the PXE control request continues to exist so that the PXE control request will take effect again the next time the server is started.

[0065] S103: Deleting the PXE boot address in the boot read-only memory of the network card device, and controlling the server to continue booting.

[0066] In a specific implementation, the PXE boot address in the boot read-only memory of the network card device is deleted, so that the network card device cannot implement PXE boot, thereby closing the PXE boot function.

[0067] The server startup control method provided by the embodiment of the present application pre-sets the corresponding relationship between the slot and the protocol identifier. By default, each network card device enables PXE startup. When the user needs to turn off the PXE startup function of the network card device corresponding to the target slot, a PXE shutdown control request is constructed according to the target protocol identifier corresponding to the target slot. According to the PXE shutdown control request, the PXE startup address in the startup read-only memory of the network card device is deleted, so that the network card device cannot realize PXE startup, and the PXE startup function is turned off. It can be seen that the present application realizes the PXE startup control of the network card device corresponding to any slot.

[0068] The embodiment of the present application discloses a server startup control method. Compared with the previous embodiment, this embodiment further explains and optimizes the technical solution. Specifically:

[0069] See also Figure 2 , a flowchart of another server startup control method according to an exemplary embodiment is shown, such as Figure 2 As shown, including:

[0070] S201: Control the server startup, scan the startup device during the startup process of the server, if a network card device is scanned, enter S202, otherwise enter S211;

[0071] S202: Determine whether the network card device has a boot read-only memory; if so, proceed to S203; if not, proceed to S211;

[0072] S203: Determine whether there is a PXE control request corresponding to the network card device; if yes, proceed to S204; if not, proceed to S211;

[0073] The PXE control request includes a target protocol identifier corresponding to the target slot where the network card device is located and a PXE startup state, and the PXE startup state includes an on state and a off state;

[0074] S204: Determine whether the PXE startup state in the PXE control request is a shutdown state; if so, proceed to S205; if not, proceed to S211;

[0075] S205: Obtaining a target correspondence relationship; wherein the target correspondence relationship is used to record the correspondence between the slot, the protocol identifier, the slot identifier, and the bus address range;

[0076] In a specific implementation, the corresponding relationship among the slot, the protocol identifier, the slot identifier, and the bus address range is preset.

[0077] S206: determining a corresponding target slot according to the target protocol identifier in the PXE control request, and determining a corresponding target slot identifier and a target bus address range in the target corresponding relationship according to the target slot;

[0078] In a specific implementation, if there is a PXE control shutdown request, the corresponding target slot is determined according to the target protocol identifier, and the corresponding target slot identifier and target bus address range are determined according to the target slot in the target corresponding relationship.

[0079] S207: Obtain the slot identifiers of all boot devices through the peripheral component interconnection standard protocol, and determine whether the target slot identifier exists; if so, proceed to S208; if not, proceed to S211;

[0080] In a specific implementation, the slot identifiers of all boot devices are obtained through the PCI (Peripheral Component Interconnect) protocol to determine whether the target slot identifier exists. If so, enter S208. If not, it means that the received PXE control shutdown request is wrong, and the server is directly controlled to continue booting.

[0081] S208: Determine that the boot device whose slot identifier is the target slot identifier is the network card device;

[0082] S209: reading the target bus address of the network card device through the input and output ports, and determining whether the target bus address is within the target bus address range; if so, proceeding to S210; if not, proceeding to S211;

[0083] In a specific implementation, the target bus address of the corresponding network card device is read according to the target slot identifier through the input and output port to determine whether the target bus address is within the target bus address range. If so, enter S210; if not, enter S211.

[0084] S210: Delete the PXE boot address in the boot read-only memory of the network card device and enter S211;

[0085] In a specific implementation, if the target bus address is within the target bus address range, the storage location of the PXE boot address of the network card device is determined according to the target bus address through the PCI protocol, and the server is controlled to continue booting after the PXE boot address is deleted.

[0086] S211: Control the server to continue starting.

[0087] It can be seen that this embodiment binds the slot and the protocol identifier to each other, and then locates and confirms the storage location of the PXE boot address by obtaining the slot identifier and the bus address of the corresponding network card device, and clears or retains the PXE boot address, thereby controlling whether the PXE boot is turned on and realizing the PXE boot control of the network card device corresponding to any slot.

[0088] The following describes an application example provided by the present application. Table 1 shows the matching of the ipmi protocol code and the slot number.

[0089] Table 1

[0090]

[0091] The "ipmi raw 0x3c 0x36 xxx xx x" command can be used to obtain the information on the opening and closing of the PXE device control corresponding to each slot port, where xxx is the IPMI protocol code in Table 1, xx is the opening or closing state, and x represents whether it is effective once or permanently. 0x1 represents opening the control of the IPMI slot PXE, and 0x00 represents not opening the control of the IPMI slot PXE. 0 represents permanent effect, and 0x1 represents one-time effect.

[0092] At startup, the network card device must be checked first. After the network card device is detected, the control will be handed over to the BootROM of the network card. The code in the BootROM will first perform a self-check to ensure that the network interface and PXE functions are normal. Therefore, by searching for the network card device on the specified slot and then controlling whether to load the BootROM execution, it is possible to close the PXE startup without affecting the communication function of the network card. The specific steps are as follows: ① After starting, the machine will first scan the startup device, including the startup information of the hard disk, network card PXE, CD, U disk and other devices. ② Determine whether it is a network card device. If not, continue to start normally. If it is a network card device, proceed to the next step. ③ Determine whether the network card has BootROM, which can be confirmed by the 0x55AA flag bit of rom FW. ④ After confirming that there is BootROM, determine whether there is an ipmi start and stop request. If there is no request, continue to start normally. If there is a shutdown request, proceed to the next step. ⑤ After receiving the shutdown request, the location information of the memory address stored in the BootROM is cleared, and the system boot cannot capture the PXE boot information, achieving the purpose of failing to PXE boot. After clearing, the server continues the normal boot process.

[0093] In order to match the pxe port of the corresponding slot with the ipmi command, it is necessary to implement the binding identification of the slot through the Slot ID (slot identification). The Slot ID helps identify each PCIe device and allows users to configure the device's priority, bandwidth allocation and other settings. The operating system and BIOS use the Slot ID to allocate and manage the resources of the PCIe device, such as interrupt request (IRQ), I / O (input / output) address space and memory mapping area. For PCIe devices that support hot plugging, the Slot ID helps the system identify the insertion and removal of the device, allowing dynamic configuration and management of resources. Therefore, during the startup phase, we can match the slots by obtaining the Slot ID information and interacting with the ipmi interaction protocol of the BMC (Baseboard Management Controller). Combined with the BUS (bus) number range corresponding to each slot, we can confirm whether PXE is the slot we want to operate at that time. The specific correspondence can be shown in Table 2:

[0094] Table 2

[0095]

[0096] After the corresponding relationship has been clarified, the following operations are performed. First, the ipmi command is received to close the BootROM, for example: ① Close slot 1 permanently, and receive the request of ipmi raw 0x3c 0x360xb1 0x0 0x0 from BMC according to the interactive protocol. ② Obtain the Slot ID information of all devices through the pci protocol, and determine whether the Slot ID information is the Slot ID of slot 1 (0x10). ③ If it is 0x10, read the BUS number information of the device to which the network card belongs through the I / O port to see if it is between 0x00 and 0x10. ④ If the BUS number is between 0x00 and 0x10, grab the option rom base address of this network card through the pci protocol ⑤ After clearing the corresponding option rom base position of this network card, continue the normal startup operation and complete the entire PXE startup disable process.

[0097] A server startup control device provided in an embodiment of the present application is introduced below. The server startup control device described below and the server startup control method described above can be referenced to each other.

[0098] See also Figure 3 , according to an exemplary embodiment, a structural diagram of a server startup control device is shown, such as Figure 3As shown, including:

[0099] The detection module 301 is used to control the server startup and detect the network card device during the startup process of the server;

[0100] The first judgment module 302 is used to judge whether there is a PXE shutdown control request corresponding to the network card device; if so, the work flow of the deletion module is started; wherein the PXE shutdown control request corresponding to the network card device includes a target protocol identifier corresponding to the target slot where the network card device is located;

[0101] The deletion module 303 is used to delete the PXE boot address in the boot read-only memory of the network card device and control the server to continue booting.

[0102] The server startup control device provided by the embodiment of the present application pre-sets the corresponding relationship between the slot and the protocol identifier. By default, each network card device enables PXE startup. When the user needs to turn off the PXE startup function of the network card device corresponding to the target slot, a PXE shutdown control request is constructed according to the target protocol identifier corresponding to the target slot. The PXE startup address in the startup read-only memory of the network card device is deleted according to the PXE shutdown control request, so that the network card device cannot realize PXE startup, and the PXE startup function is turned off. It can be seen that the present application realizes the PXE startup control of the network card device corresponding to any slot.

[0103] Based on the above embodiment, as a preferred implementation, the detection module 301 is specifically used for: scanning the startup device during the startup process of the server; if a network card device is scanned, starting the work flow of the first judgment module 302.

[0104] Based on the above embodiment, as a preferred implementation, it also includes:

[0105] The second judgment module is used to judge whether the network card device has a startup read-only memory; if it does, the working process of the first judgment module 302 is started.

[0106] Based on the above embodiment, as a preferred implementation mode, the first judgment module 302 is specifically used to: determine whether there is a PXE control request corresponding to the network card device; wherein the PXE control request includes a target protocol identifier and a PXE startup status corresponding to the target slot where the network card device is located, and the PXE startup status includes an on state and a off state; if there is a PXE control request corresponding to the network card device, determine whether the PXE startup status in the PXE control request is a off state; if the PXE startup status in the PXE control request is a off state, determine that there is a PXE control request corresponding to the network card device.

[0107] Based on the above embodiment, as a preferred implementation mode, the PXE control request further includes a validity type, and the validity type includes a one-time validity and a permanent validity.

[0108] Based on the above embodiment, as a preferred implementation, it also includes:

[0109] The receiving module is used to receive the PXE shutdown control request corresponding to the network card device through the intelligent platform management interface.

[0110] Based on the above embodiment, as a preferred implementation, it also includes:

[0111] An acquisition module, used to acquire a target correspondence relationship; wherein the target correspondence relationship is used to record the correspondence between the slot, the protocol identifier, the slot identifier, and the bus address range;

[0112] Correspondingly, the deletion module 303 is specifically used to: determine the corresponding target slot according to the target protocol identifier in the PXE control shutdown request, and determine the corresponding target slot identifier and target bus address range in the target corresponding relationship according to the target slot; obtain the slot identifiers of all boot devices through the peripheral component interconnection standard protocol, and determine whether the target slot identifier exists; if not, control the server to continue booting; if so, determine that the boot device with the slot identifier as the target slot identifier is the network card device; read the target bus address of the network card device through the input and output ports, and determine whether the target bus address is within the target bus address range; if so, delete the PXE boot address in the boot read-only memory of the network card device, and control the server to continue booting; if not, control the server to continue booting.

[0113] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0114] Based on the hardware implementation of the above program module, and in order to implement the method of the embodiment of the present application, the embodiment of the present application also provides an electronic device, Figure 4 FIG. 1 is a structural diagram of an electronic device according to an exemplary embodiment. Figure 4 As shown, the electronic equipment includes:

[0115] Communication interface 1, capable of exchanging information with other devices such as network devices;

[0116] The processor 2 is connected to the communication interface 1 to implement information exchange with other devices and is used to execute the server startup control method provided by one or more technical solutions when running a computer program. The computer program is stored in the memory 3.

[0117] Of course, in actual application, the various components in the electronic device are coupled together through the bus system 4. It can be understood that the bus system 4 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 4 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, Figure 4 Various buses are labeled as bus system 4.

[0118] The memory 3 in the embodiment of the present application is used to store various types of data to support the operation of the electronic device. Examples of such data include: any computer program used to operate on the electronic device.

[0119] It can be understood that the memory 3 can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and direct RAMbus random access memory (DRRAM, Direct Rambus Random Access Memory).The memory 3 described in the embodiments of the present application is intended to include but is not limited to these and any other suitable types of memories.

[0120] The method disclosed in the above embodiment of the present application can be applied to the processor 2, or implemented by the processor 2. The processor 2 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit in the processor 2 or the instruction in the form of software. The above processor 2 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The processor 2 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, which is located in the memory 3, and the processor 2 reads the program in the memory 3 and completes the steps of the above method in combination with its hardware.

[0121] When the processor 2 executes the program, the corresponding processes in the various methods of the embodiments of the present application are implemented, which will not be repeated here for the sake of brevity.

[0122] In an exemplary embodiment, the embodiment of the present application further provides a non-volatile storage medium storing a computer program, which can be executed by the processor 2 to complete the steps of the aforementioned method.

[0123] In an exemplary embodiment, the present application also provides a computer program product, including a computer program, which is executed by the processor 2 to complete the steps of the aforementioned method.

[0124] A person of ordinary skill in the art can understand that all or part of the steps of implementing the above-mentioned method embodiment can be completed by hardware related to computer program instructions, and the aforementioned computer program can be stored in a non-volatile storage medium. When the computer program is executed, it executes the steps of the above-mentioned method embodiment. Alternatively, if the above-mentioned integrated unit of the present application is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a non-volatile storage medium. Based on this understanding, the technical solution of the embodiment of the present application can be essentially or partly embodied in the form of a software product, which is stored in a non-volatile storage medium and includes a number of instructions for an electronic device (which can be a personal computer, a server, a network device, etc.) to execute all or part of the methods described in each embodiment of the present application.

[0125] The above description is only a specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application.

Claims

1. A server startup control method, characterized in that: include: Controlling the server startup and detecting the network card device during the startup process of the server; Determine whether there is a PXE shutdown control request corresponding to the network card device; wherein the PXE shutdown control request corresponding to the network card device includes a target protocol identifier corresponding to the target slot where the network card device is located; If it exists, the PXE boot address in the boot read-only memory of the network card device is deleted, and the server is controlled to continue booting.

2. The server startup control method according to claim 1, characterized in that: Detecting the network card device during the startup process of the server includes: Scanning a startup device during the startup process of the server; If a network card device is scanned, the process proceeds to the step of determining whether there is a PXE control shutdown request corresponding to the network card device.

3. The server startup control method according to claim 1, characterized in that: Before determining whether there is a PXE control shutdown request corresponding to the network card device, the method further includes: Determine whether the network card device has a startup read-only memory; If yes, the process proceeds to the step of determining whether there is a PXE control shutdown request corresponding to the network card device.

4. The server startup control method according to claim 1, characterized in that: Determining whether there is a PXE control shutdown request corresponding to the network card device includes: Determine whether there is a PXE control request corresponding to the network card device; wherein the PXE control request includes a target protocol identifier and a PXE startup state corresponding to the target slot where the network card device is located, and the PXE startup state includes an on state and a off state; If there is a PXE control request corresponding to the network card device, determining whether the PXE startup state in the PXE control request is a closed state; If the PXE startup state in the PXE control request is a shutdown state, it is determined that there is a shutdown PXE control request corresponding to the network card device.

5. The server startup control method according to claim 4, characterized in that: The PXE control request also includes a validity type, and the validity type includes a one-time validity and a permanent validity.

6. The server startup control method according to claim 1, characterized in that: Also includes: The PXE shutdown control request corresponding to the network card device is received through the intelligent platform management interface.

7. The server startup control method according to claim 1, characterized in that: Before deleting the PXE boot address in the boot read-only memory of the network card device and controlling the server to continue booting, the method further includes: Obtaining a target correspondence relationship; wherein the target correspondence relationship is used to record the correspondence between the slot, the protocol identifier, the slot identifier, and the bus address range; Correspondingly, deleting the PXE boot address in the boot read-only memory of the network card device and controlling the server to continue booting includes: Determine a corresponding target slot according to the target protocol identifier in the PXE shutdown control request, and determine a corresponding target slot identifier and a target bus address range in the target corresponding relationship according to the target slot; Obtaining slot identifiers of all boot devices through a peripheral component interconnection standard protocol, and determining whether the target slot identifier exists; If it does not exist, control the server to continue starting; If it exists, determining that the boot device whose slot identifier is the target slot identifier is the network card device; Read the target bus address of the network card device through the input and output ports, and determine whether the target bus address is within the target bus address range; If yes, then deleting the PXE boot address in the boot read-only memory of the network card device, and controlling the server to continue booting; If not, the server is controlled to continue starting.

8. A server startup control device, characterized in that: include: A detection module, used for controlling the startup of the server and detecting the network card device during the startup process of the server; A first judging module is used to judge whether there is a PXE control shutdown request corresponding to the network card device; If it exists, the workflow of the deletion module is started; wherein the PXE control request corresponding to the network card device includes the target protocol identifier corresponding to the target slot where the network card device is located; The deletion module is used to delete the PXE startup address in the startup read-only memory of the network card device and control the server to continue to start.

9. An electronic device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the steps of the server startup control method as claimed in any one of claims 1 to 7 when executing the computer program.

10. A non-volatile storage medium, characterized in that: The non-volatile storage medium stores a computer program, and when the computer program is executed, the steps of the server startup control method according to any one of claims 1 to 7 are implemented.

Images