CN118377513B

CN118377513B - Information management method and device of server

Info

Publication number: CN118377513B
Application number: CN202410835940.6A
Authority: CN
Inventors: 王向芳; 孙秀强; 张锋; 张璐
Original assignee: Suzhou Metabrain Intelligent Technology Co Ltd
Current assignee: Suzhou Metabrain Intelligent Technology Co Ltd
Priority date: 2024-06-26
Filing date: 2024-06-26
Publication date: 2024-09-27
Anticipated expiration: 2044-06-26
Also published as: CN118377513A

Abstract

The embodiment of the application provides an information management method and device of a server, wherein the method comprises the following steps: under the condition that a server is electrified or restarted, determining the type needing to be dynamically updated in a protocol specification table as a target type to obtain a target type set, wherein the type in the protocol specification table is used for recording management information of the server; determining total reserved resources according to preset resources of all target types in the target type set, wherein the preset resources are resources which are preconfigured according to management information recorded by the target types; and updating the management information of each target type in the protocol specification table through the total reserved resources. The application solves the problem of downtime of the system caused by insufficient resources for dynamically updating the SMBIOS protocol specification table in the related technology, thereby achieving the effect of improving the stability of the system.

Description

Information management method and device of server

Technical Field

The embodiment of the application relates to the field of computers, in particular to an information management method and device of a server.

Background

Electronic products such as a server, a desktop, a notebook, a mobile phone and the like all need to view management information of the system under an operating system, and the configuration information of the server system is conveniently and quickly checked in real time by using personnel or operation and maintenance personnel by uniformly collecting and summarizing all information on a main board and updating the information to an SMBIOS protocol specification table of the BIOS for recording, so that the configuration of the whole machine can be known without physically and practically contacting with server equipment.

The SMBIOS protocol specification table has two dynamic and static updating modes, wherein the data of the static updating mode is not changed dynamically along with the change of the server configuration, and the real-time performance and accuracy of the information cannot be ensured; while the dynamic updating mode can ensure that the information in the system is updated in time along with the change of hardware configuration, the byte data length of each type is not fixed, and if the reserved byte number or length is insufficient, the data exceeding the reserved byte cannot be supported, and serious fatal problems such as error reporting and downtime occur to the system.

There is currently no effective solution to the above problems.

Disclosure of Invention

The embodiment of the application provides an information management method and device of a server, which at least solve the problem of system downtime caused by insufficient resources for dynamically updating an SMBIOS protocol specification table in the related art.

According to an embodiment of the present application, there is provided an information management method of a server, including: under the condition that a server is electrified or restarted, determining the type needing to be dynamically updated in a protocol specification table as a target type to obtain a target type set, wherein the type in the protocol specification table is used for recording management information of the server; determining total reserved resources according to preset resources of each target type in the target type set, wherein the preset resources are resources which are preconfigured according to management information recorded by the target type; and updating the management information of each target type in the protocol specification table through the total reserved resources.

In an exemplary embodiment, determining the total reserved resource according to the preset resources of each target type in the target type set includes: determining the type of the management information recorded in the target type set and related to the hardware quantity as a first target type, and obtaining a first target type set; determining the type of the management information recorded in the target type set, which is irrelevant to the quantity of hardware, as a second target type, and obtaining a second target type set; determining the sum of preset resources of each type in the first target type set as a first preset resource sum, and determining the sum of preset resources of each type in the second target type set as a second preset resource sum; and determining the sum of the first preset resource sum and the second preset resource sum as the total reserved resource.

In an exemplary embodiment, determining the sum of the reserved resources of the first set of target types and the reserved resources of the second target as the total reserved resources comprises: the total reserved resources are obtained by the following formula:

Wherein T is the total reserved resource, α _i is the hardware quantity of the ith target type in the first target type set, N, M is an integer greater than or equal to 1, S _i is the preset resource of the ith target type, and β _j is the preset resource of the jth target type in the second target type set.

In an exemplary embodiment, determining a type of management information related to the number of hardware recorded in the target type set as a first target type, to obtain a first target type set, including: determining type 4, type 9, type 17, type 18, type 19 and type 39 in the protocol specification table as the first target type, wherein the type 4 is used for recording CPU information of a central processing unit of the server, the management information comprises the CPU information, the hardware quantity comprises the quantity of CPUs in the server, the type 9 is used for recording PCI interface information of peripheral components of the server, the hardware quantity comprises the quantity of PCI in the server, the type 17, type 18 and type 19 are used for recording memory information of the server, the hardware quantity comprises the quantity of memory in the server, the type 39 is used for recording power supply information of the server, and the hardware quantity comprises the quantity of power supplies in the server.

In an exemplary embodiment, determining the type of the management information which is irrelevant to the hardware quantity and is recorded in the target type set as a second target type, to obtain a second target type set, including: and determining the type 0, the type 1, the type 2, the type 3, the type 12, the type 20 and the type 41 in the protocol specification table as a second target type, wherein the type 0, the type 1, the type 2 and the type 3 are used for recording Field Replaceable Unit (FRU) information of the server, the type 12 is used for recording physical silk-screen information, the type 20 is used for recording a communication protocol of a basic input and output system and a baseboard management controller of the server, and the type 41 is used for recording on-board equipment information of the server.

In an exemplary embodiment, after said determining total reserved resources according to preset resources of each of said target types in said set of target types, said method further comprises: and updating the total reserved resources into a Basic Input Output System (BIOS) mirror image and restarting the server.

In an exemplary embodiment, after restarting the server, updating management information of each of the target types in the protocol specification table includes: after entering a DXE phase of a driver execution environment and before ending the DXE phase, acquiring current latest FRU information through a basic input output system BIOS; and updating the current latest FRU information to the type 0, the type 1, the type 2 and the type 3 in the protocol specification table.

In an exemplary embodiment, after determining that the type 0, type 1, type 2, and type 3 are updated, the method further includes: acquiring current latest Central Processing Unit (CPU) information, and updating the latest CPU information to a type 4, wherein the CPU information comprises: CPU manufacturer, CPU model, CPU speed, CPU core number; after the update to the type 4 is determined, acquiring current latest physical silk-screen information, and updating the current latest physical silk-screen information to the type 12; after the update of the type 12 is determined, acquiring current latest memory information, and updating the memory information to the type 17, the type 18 and the type 19, wherein the memory information comprises the memory quantity, the memory slot silk screen information, the memory capacity, the memory manufacturer and the memory supported functional characteristics; after the update of the type 17, the type 18 and the type 19 is determined, the communication protocol of the latest basic input output system and the baseboard management controller is acquired, and the communication protocol of the latest basic input output system and the baseboard management controller is updated to the type 20.

In an exemplary embodiment, after determining that the type 20 is updated, the method further includes: acquiring the latest power supply information and updating the latest power supply information to a type 39, wherein the power supply information comprises: power supply manufacturer, power supply delivery date, power supply in-place information and power supply position information; after the update of the type 39 is determined, the latest on-board device information is acquired, and the latest on-board device information is updated to the type 41, wherein the on-board device information comprises the position information of an on-board storage medium.

In an exemplary embodiment, after determining that the type 41 is updated, the method further includes: after the DXE phase is finished and before the DXE phase enters an operating system, the latest PCI interface information of the peripheral component interconnection is obtained; and updating the PCI interface information to the type 9.

In an exemplary embodiment, after updating the management information of each of the target types in the protocol specification table by the total reserved resource, the method further includes: after the protocol specification table is updated, determining the total resource requirement of the protocol specification table and applying for a corresponding memory space.

According to another embodiment of the present application, there is provided an information management apparatus of a server including: the system comprises an acquisition module, a storage module and a control module, wherein the acquisition module is used for determining the type which needs to be dynamically updated in a protocol specification table as a target type under the condition that a server is powered on or restarted to obtain a target type set, wherein the type in the protocol specification table is used for recording management information of the server; the determining module is used for determining total reserved resources according to preset resources of each target type in the target type set, wherein the preset resources are resources which are preconfigured according to management information recorded by the target type; and the updating module is used for updating the management information of each target type in the protocol specification table through the total reserved resources.

According to a further embodiment of the application, there is also provided a computer readable storage medium having stored therein a computer program, wherein the computer program is arranged to perform the steps of any of the method embodiments described above when run.

According to a further embodiment of the application there is also provided an electronic device comprising a memory having stored therein a computer program and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.

According to a further embodiment of the application, there is also provided a computer program product comprising a computer program which, when executed by a processor, implements the steps of any of the method embodiments described above.

According to the method and the device, under the condition that the server is powered on or restarted, the type which needs to be dynamically updated in the protocol specification table is determined as the target type, and the target type set is obtained, wherein the type in the protocol specification table is used for recording management information of the server; determining total reserved resources according to preset resources of all target types in the target type set, wherein the preset resources are resources which are preconfigured according to management information recorded by the target types; and updating the management information of each target type in the protocol specification table through the total reserved resources.

The total reserved byte number is calculated by calculating the number of the actual words required by the type in each SMBIOS protocol specification table, so that the problem of system downtime caused by insufficient resources for dynamically updating the SMBIOS protocol specification table in the related technology can be solved, and the effect of improving the stability of the system is achieved.

Drawings

Fig. 1 is a hardware configuration block diagram of a server apparatus of an information management method of a server according to an embodiment of the present application;

fig. 2 is a flowchart of an information management method of a server according to an embodiment of the present application;

FIG. 3 is a schematic diagram of the physical connection of a server motherboard according to an embodiment of the present application;

FIG. 4 is a particular flow diagram of updating an SMBIOS protocol specification table in accordance with an embodiment of the present application;

FIG. 5 is a swim lane diagram of an updated SMBIOS protocol specification table, in accordance with an embodiment of the present application;

Fig. 6 is a block diagram of an information management apparatus of a server according to an embodiment of the present application.

Detailed Description

To aid in a better understanding of embodiments of the application, some of the terms are explained below:

Smbase: SYSTEM MANAGEMENT BIOS, unified specifications that the motherboard or system manufacturer needs to follow to display product management information in a standard format. The SMBIOS (SYSTEM MANAGEMENT BIOS) protocol specification table is a standard format for describing computer hardware configuration information, and contains details about various hardware components of a computer system, such as a processor, memory, motherboard, graphics card, etc. The SMBIOS protocol specification table can be read by an operating system or a software program so as to identify, configure and manage the system, and by reading the SMBIOS protocol specification table, a user can know the specific configuration information of the computer hardware, so that the performance and the function of the computer system are better known.

BIOS: basic Input Output System, basic input output system.

BMC: baseboard Management Controller, a baseboard management controller.

TYPE: one of the type information of the SMBIOS table.

Type39: one type of power information display of the SMBIOS protocol.

PSU: power supply unit, a power supply.

I2C: inter-INTEGRATED CIRCUIT, two-wire serial bus.

IPMI: INTELLIGENT PLATFORM MANAGEMENT INTERFACE, an intelligent platform management interface.

Run time: and a stage of running code under BIOS system.

PCI: PERIPHERAL COMPONENT INTERCONNECT a standard interface for connecting internal components of a computer. It is a bus technology for high-speed data transmission, and is used for connecting various peripheral devices, such as display card, network card and sound card. PCI interfaces are typically found on a computer motherboard in the form of slots into which various PCI cards may be inserted to extend the functionality of the computer. There are many different versions of the PCI interface, such as PCI Express (PCIe), which is an upgraded version of PCI, with higher transmission speeds and better performance.

FRU: FIELD REPLACEMENT Units, field replaceable Units, in baseboard management controllers, FRUs generally refer to components or modules that can be replaced by a user or technician, such as batteries, fans, power supplies, etc., which can assist maintenance personnel in quickly repairing a failure or upgrading a system.

DXE: driver Execution Environment, a driver execution environment, which refers to the execution environment and resources required by a driver when executing in an operating system. In this environment, drivers may interact with hardware devices to perform various operations to enable control and management of the devices. The driver execution environment typically includes components such as an operating system provided related API interface, a device driver framework, a device manager, and the like.

BDS: boot DEV SELECT, initiate device selection.

Embodiments of the present application will be described in detail below with reference to the accompanying drawings in conjunction with the embodiments.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order.

The method embodiments provided in the embodiments of the present application may be executed in a server apparatus or similar computing device. Taking the operation on the server device as an example, fig. 1 is a block diagram of the hardware structure of the server device of a method for managing information of a server according to an embodiment of the present application. As shown in fig. 1, the server device may include one or more (only one is shown in fig. 1) processors 102 (the processor 102 may include, but is not limited to, a microprocessor MCU, a programmable logic device FPGA, or the like processing means) and a memory 104 for storing data, wherein the server device may further include a transmission device 106 for communication functions and an input-output device 108. It will be appreciated by those of ordinary skill in the art that the architecture shown in fig. 1 is merely illustrative and is not intended to limit the architecture of the server apparatus described above. For example, the server device may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.

The memory 104 may be used to store a computer program, for example, a software program of application software and a module, such as a computer program corresponding to an information management method of a server in an embodiment of the present application, and the processor 102 executes the computer program stored in the memory 104 to perform various functional applications and data processing, that is, to implement the above-mentioned method. Memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory remotely located with respect to the processor 102, which may be connected to the server device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device 106 is used to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of a server device. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, simply referred to as a NIC) that can connect to other network devices through a base station to communicate with the internet. In one example, the transmission device 106 may be a Radio Frequency (RF) module, which is configured to communicate with the internet wirelessly.

In this embodiment, there is provided an information management method of a server, and fig. 2 is a flowchart of an information management method of a server according to an embodiment of the present application, as shown in fig. 2, the flowchart includes the steps of:

step S202, under the condition that a server is powered on or restarted, determining the type needing to be dynamically updated in a protocol specification table as a target type to obtain a target type set, wherein the type in the protocol specification table is used for recording management information of the server;

The above type may be a type in a protocol specification table, for example, type 0, type 1, type 2, type 3, etc., and the type is used for recording configuration information of a motherboard, for example, the number of CPU processors, CPU rate, CPU core, memory number, memory core, memory vendor, PCI slot device number, motherboard on-board device number, system vendor, system model, motherboard model, etc.; the protocol specification table may be an SMBIOS protocol specification table, and the type updating manner of the protocol specification table may be a static updating manner or a dynamic updating manner, where the static updating manner is that when the BIOS starts, all information of the motherboard is pre-filled in the system, and when the BIOS starts, the information is filled in and updated to each type of the SMBIOS protocol, but the data is static and not changed dynamically with the change of the server configuration; when the dynamic updating mode is to start, the BIOS actively identifies the number of CPU processors, the CPU speed, the CPU cores, the memory quantity, the memory cores, the memory manufacturer, the PCI slot equipment quantity, the mainboard on-board equipment quantity, the system manufacturer, the system model, the mainboard model and the like which are related to the starting to dynamically update, so that the real-time performance and the accuracy of information are maintained, and the efficiency and the accuracy of system management are improved. It should be noted that, in the embodiment of the present application, a dynamic update mode is adopted by default.

Under the condition of powering up or restarting a server, after the SMBIOS protocol specification table is updated, starting to enter a shell environment or an operating system; after the operation system is entered, the type of the SMBIOS protocol specification table is analyzed by utilizing the SMBIOS analysis command carried by the system, the type needing dynamic update in the protocol specification table is obtained, the type needing dynamic update in the protocol specification table comprises a plurality of information such as main board information, CPU information, memory information, PCI slot equipment information, power supply information, main board on-board information and the like, the type needing dynamic update in the protocol specification table is determined as a target type, and a target type set is obtained.

Step S204, determining total reserved resources according to preset resources of each target type in the target type set, wherein the preset resources are resources which are preconfigured according to management information recorded by the target type;

The target type may be a type that dynamically updates the SMBIOS table before the DXE startup phase of the BIOS is completed, or a type that updates the SMBIOS table after the DXE startup phase of the BIOS is completed and before entering the operating system; the reserved resource may be the number or length of bytes required by each type in the protocol specification table, wherein the type of the SMBIOS protocol specification table is dynamically updated before the DXE startup phase of the BIOS is finished, and the reserved number of bytes is calculated by adding the number of bytes of the current SMBIOS protocol specification table to the reserved number of bytes and the number of bytes of the type of the current SMBIOS protocol specification table; the total reserved resource may be a server; if the type update byte count of the SMBIOS protocol specification table after the DXE startup phase of the BIOS is completed, the previously reserved byte count, including the updated FRU information length size, will also occupy the reserved byte count. In addition, the PCI slot information update of type 9 of the SMBIOS protocol specification table also occupies the previously reserved byte count, entering a pre-Operating System (OS) stage after the DXE ends.

The preset resources may be the size of byte resources that need to be reserved for each type, for example, the type 0 has a length of 100 bytes, and the type 1 has a length of 110 bytes; type 2 is 120 bytes in length; type 3 is 200 bytes in length; the length of type 4 is 200 bytes for 1 CPU, but 400 bytes are needed for 2 CPUs, and 800 bytes or 1600 bytes are needed for 4 CPUs or 8 CPUs; type 12 is 100 bytes in length; 1 memory time type 17 is 200 bytes in length, type 18 is 200 bytes in length, type 19 is 200 bytes in length; when 32 memories are used, types 17, 18, 19 and the like all need to be multiplied by a multiple of 32; type 20 is 100 bytes in length; the length of type 39 is 100 bytes for 1 power supply, and 200 bytes for 2 power supplies; type 41 is 100 bytes in length; type 9 is 100 bytes long for 1 PCI device, and 32 bytes are needed when 32 PCI devices are present.

Specifically, determining the type of the management information and the hardware quantity which are recorded in the target type set as a first target type, and obtaining a first target type set; determining the type of the management information recorded in the target type set, which is irrelevant to the quantity of hardware, as a second target type, and obtaining a second target type set; determining the sum of preset resources of each type in the first target type set as a first preset resource sum, and determining the sum of preset resources of each type in the second target type set as a second preset resource sum; and determining the sum of the first preset resource sum and the second preset resource sum as the total reserved resource.

The first target type may be types 17, 18, 19, etc., for example, type 17 has a length of 200 bytes, type 18 has a length of 200 bytes, and type 19 has a length of 200 bytes for 1 memory; when 32 memories are used, types 17, 18, 19 and the like all need to be multiplied by a multiple of 32; the second target type may be type 0, 1,2, 4, etc., for example, type 0 has a length of 100 bytes and type 1 has a length of 110 bytes; type 2 is 120 bytes in length; type 3 is 200 bytes in length; the method comprises the steps of respectively obtaining a first target type set and a second target type set, determining preset resources and preset resource sum of each type in the first target type set and the second target type set, and determining total reserved resources according to the preset resource sum of the first target type set and the preset resource sum combined by the second target type set.

By classifying the types in the SMBIOS protocol specification table and calculating reserved resources respectively, the reserved byte number of the type of the SMBIOS protocol specification table required by the maximum configuration of the server is obtained, and a system manager and an engineer can be helped to plan and manage the configuration of the server better, so that the stable operation of the system is ensured, and the performance requirement is met. Meanwhile, the reserved byte number of the SMBIOS protocol specification table type required by server configuration is known, so that the system resource allocation can be better optimized, and the system performance and efficiency are improved.

Step S206, updating the management information of each target type in the protocol specification table through the total reserved resources.

Through the steps, under the condition that a server is electrified or restarted, the type needing to be dynamically updated in a protocol specification table is determined to be a target type, and a target type set is obtained, wherein the type in the protocol specification table is used for recording management information of the server; determining total reserved resources according to preset resources of each target type in the target type set, wherein the preset resources are resources which are preconfigured according to management information recorded by the target type; and updating the management information of each target type in the protocol specification table through the total reserved resources.

The maximum byte number which is actually needed to be reserved is calculated in a maximized mode through the server configuration information after the operation system is started and is used before the operation system is started after the DXE phase is finished, the problem that the system is down due to insufficient resources for dynamically updating the SMBIOS protocol specification table in the related technology is solved, and the stability of the system is improved.

The main execution body of the above steps may be a server, a terminal, or the like, but is not limited thereto.

As an alternative embodiment, determining the sum of the reserved resources of the first set of target types and the reserved resources of the second target as the total reserved resources comprises: the total reserved resources are obtained by the following formula:

The total number of reserved bytes is calculated by calculating the number of actual words required by the type of each SMBIOS protocol specification table, so that the reserved bytes are ensured not to occupy excessive memory resources, and the problem of starting downtime of the system caused by configuration and reconfiguration of the system or a server is avoided.

As an optional implementation manner, determining the type of the management information and the hardware quantity recorded in the target type set as a first target type, to obtain a first target type set, including: determining type 4, type 9, type 17, type 18, type 19 and type 39 in the protocol specification table as the first target type, wherein the type 4 is used for recording CPU information of a central processing unit of the server, the management information comprises the CPU information, the hardware quantity comprises the quantity of CPUs in the server, the type 9 is used for recording PCI interface information of peripheral components of the server, the hardware quantity comprises the quantity of PCI in the server, the type 17, type 18 and type 19 are used for recording memory information of the server, the hardware quantity comprises the quantity of memory in the server, the type 39 is used for recording power supply information of the server, and the hardware quantity comprises the quantity of power supplies in the server.

As an optional implementation manner, determining the type of the management information which is irrelevant to the hardware quantity and is recorded in the target type set as a second target type, to obtain a second target type set, which includes: and determining the type 0, the type 1, the type 2, the type 3, the type 12, the type 20 and the type 41 in the protocol specification table as a second target type, wherein the type 0, the type 1, the type 2 and the type 3 are used for recording Field Replaceable Unit (FRU) information of the server, the type 12 is used for recording physical silk-screen information, the type 20 is used for recording a communication protocol of a basic input and output system and a baseboard management controller of the server, and the type 41 is used for recording on-board equipment information of the server.

As an optional implementation manner, after the determining total reserved resources according to the preset resources of each target type in the target type set, the method further includes: and updating the total reserved resources into a Basic Input Output System (BIOS) mirror image and restarting the server.

The total reserved resources are updated to the BIOS mirror image, so that the resources can be ensured to be correctly configured and allocated when the system is started, and the utilization of the system resources is optimized, thereby improving the stability and reliability of the system, improving the system performance and reducing the resource waste, simultaneously reducing the resource configuration and allocation problems which need to be concerned by management staff, and simplifying the system management and maintenance work.

As an optional embodiment, after restarting the server, updating management information of each of the target types in the protocol specification table includes: after entering a DXE phase of a driver execution environment and before ending the DXE phase, acquiring current latest FRU information through a basic input output system BIOS; and updating the current latest FRU information to the type 0, the type 1, the type 2 and the type 3 in the protocol specification table.

As an optional embodiment, after determining that the type 0, type 1, type 2, and type 3 are updated, the method further includes: acquiring current latest Central Processing Unit (CPU) information, and updating the latest CPU information to a type 4, wherein the CPU information comprises: CPU manufacturer, CPU model, CPU speed, CPU core number; after the update to the type 4 is determined, acquiring current latest physical silk-screen information, and updating the current latest physical silk-screen information to the type 12; after the update of the type 12 is determined, acquiring current latest memory information, and updating the memory information to the type 17, the type 18 and the type 19, wherein the memory information comprises the memory quantity, the memory slot silk screen information, the memory capacity, the memory manufacturer and the memory supported functional characteristics; after the update of the type 17, the type 18 and the type 19 is determined, the communication protocol of the latest basic input output system and the baseboard management controller is acquired, and the communication protocol of the latest basic input output system and the baseboard management controller is updated to the type 20.

As an alternative embodiment, after determining that the type 20 is updated, the method further includes: acquiring the latest power supply information and updating the latest power supply information to a type 39, wherein the power supply information comprises: power supply manufacturer, power supply delivery date, power supply in-place information and power supply position information; after the update of the type 39 is determined, the latest on-board device information is acquired, and the latest on-board device information is updated to the type 41, wherein the on-board device information comprises the position information of an on-board storage medium.

As an alternative embodiment, after determining that the type 41 is updated, the method further includes: after the DXE phase is finished and before the DXE phase enters an operating system, the latest PCI interface information of the peripheral component interconnection is obtained; and updating the PCI interface information to the type 9.

As an optional implementation manner, after updating the management information of each target type in the protocol specification table through the total reserved resource, the method further includes: after the protocol specification table is updated, determining the total resource requirement of the protocol specification table and applying for a corresponding memory space.

As an optional implementation manner, before the server is started, the BIOS is set to be statically updated, the SMBIOS protocol specification table is not changed according to the original scheme, and when the server is started, the BIOS updates the type data in the SMBIOS protocol update table in a dynamic update mode, wherein part of the type data in the SMBIOS protocol specification table is updated before the DXE phase is ended, and part of the type data in the SMBIOS protocol specification table is updated after the DXE is started and before the SMBIOS protocol specification table enters an operating system. The method has the advantages that the stage data of the original updated SMBIOS protocol specification table is kept unchanged in a dynamic mode, the maximum byte number actually required to be reserved is calculated in a maximized mode through the server configuration information after entering an operating system, and the maximum byte number is used before entering the system after the DXE stage is finished, so that the operation states of the system in different stages are accurate, system errors or crashes caused by inconsistent data are avoided, the compatibility of the system and external equipment or software is ensured, and the situation of mismatching or unsupported is avoided; meanwhile, configuration and resource allocation of the system are optimized, more accurate and detailed system information is provided, management and maintenance work of a system administrator are facilitated, performance of the system is improved, the system is more stable, reliable, compatible and efficient, and use experience of a user and overall performance of the system are improved.

As an alternative implementation, fig. 3 is a schematic physical connection diagram of a server motherboard according to an embodiment of the present application, as shown in fig. 3, configuration information of a server is transmitted to a Central Processing Unit (CPU) of the server through a PCI bus or an I2C bus by a dual-sided memory module (DIMM), two CPUs (CPU 0 and CPU 1) are connected by a novel efficient interconnection protocol (UPI/CCIX/GMIX), a BIOS is connected to the central processing unit (CPU 0) by a serial peripheral interface (SPI/QSPI/ESPI), a BMC is connected to a Power Supply (PSU), a graphics display interface (VGA), and the central processing unit (CPU 0), a built-in device (OnboardDevice) is connected to the central processing unit (CPU 0) by a PCI bus, and the CPUs are connected to each other, so that an smbs protocol specification table is updated.

As an alternative implementation, fig. 4 is a specific flowchart of updating the SMBIOS protocol specification table according to an embodiment of the present application, as shown in fig. 4, applied to the server motherboard shown in fig. 3, where the specific flowchart is as follows:

step S1, when a server is started, BIOS updates the type data in an SMBIOS protocol update table in a dynamic update mode, and does not support a static update mode, because the static update mode needs to fix various configuration information and PCI slot information and other character information in type 9 in advance;

Step S2, after BIOS setting static update, the SMBIOS does not change according to the original scheme design, part of the type of the SMBIOS protocol specification table is updated before the DXE phase is finished, and part of the type data of the SMBIOS protocol specification table is updated after the DXE is started and before the SMBIOS enters an operating system;

Step S3, after the SMBIOS protocol specification table is updated, starting to enter a shell environment or an operating system; after entering an operating system, analyzing the type of the SMBIOS protocol specification table by utilizing an SMBIOS analysis command carried by the system;

Step S4, after the analysis data is obtained, calculating the size of reserved byte resources required by the types, such as 0, 1, 2,3, 4, 12, 17, 18, 19, 20, 39, 41, 9 and the like; if the type 0 is 100 bytes in length, the type 1 is 110 bytes in length, the type 2 is 120 bytes in length, the type 3 is 200 bytes in length, the type 4 is 200 bytes in length for 1 CPU, but 400 bytes are needed for 2 CPUs, 800 bytes or 1600 bytes are needed for 4 CPUs or 8 CPUs, the type 12 is 100 bytes in length, the type 17 is 200 bytes in length for 1 memory, the type 18 is 200 bytes in length, and the type 19 is 200 bytes in length; when 32 memories are used, types 17, 18, 19 and the like all need to be multiplied by a multiple of 32; the length of type 20 is 100 bytes, the length of type 39 is 100 bytes when 1 power supply, the length of type 41 is 100 bytes when 2 power supplies, the length of type 9 is 100 bytes when 1 PCI device, and the number of bytes is 32 times when 32 PCI devices appear;

Step S5, after the bytes are calculated, accumulating the accumulated byte number to obtain reserved byte number of the type of the SMBIOS protocol specification table required by the maximum configuration of the server, updating the data to the BIOS mirror image and restarting the server;

Step S6, after restarting the server, updating table types 0, 1,2 and 3 in the SMBIOS protocol before ending the DXE stage, wherein partial character strings of the data existence types 0, 1,2 and 3 are acquired through updating FRU information under the system, and meanwhile, partial information is reserved in the types 0, 1,2 and 3 of the SMBIOS protocol specification table in advance;

Step S7, after the types 0,1, 2 and 3 are updated, continuing to update the type 4 in the SMBIOS protocol specification table, wherein the type 4 is information of recording the current CPU, including but not limited to CPU manufacturer, CPU model, CPU speed, CPU core number and the like;

Step S8, after the Type 4 is updated, updating the Type 12 of the SMBIOS protocol, wherein the Type 12 mainly relates to physical silk-screen information of the link between the main board and the peripheral, and updating memory related information, namely Type17, type 18, type 19 and the like after the update is finished;

Step S9, updating the types 17, 18 and 19 of the SMBIOS protocol specification table, wherein the types 17, 18 and 19 mainly relate to the memory quantity, memory slot silk-screen information, memory capacity, memory manufacturers, memory supported functional characteristics and the like of the current server;

Step S10, after the memory information of the types 17, 18 and 19 is updated, sequentially updating the type 20 of the SMBIOS protocol specification table, wherein the type 20 mainly records the communication protocol of the BIOS and the BMC;

step S11, after updating SMIOS of type 20, updating type 39 of SMBIOS protocol, wherein type 39 mainly relates to power supply equipment of a server, namely PSU power supply information, including power supply related information such as power supply manufacturer, power supply delivery date, power supply in-place information, power supply position information and the like;

Step S12, after the type 39 is updated, updating the type 41, wherein the type 41 mainly relates to on-board equipment of a main board, and comprises position information of an on-board storage medium and the like;

Step S13, updating type 9 information of the SMBIOS protocol after the DXE stage is finished and before the DXE stage enters an operating system, wherein the type 9 information is mainly PCI slot information, including but not limited to core information such as slot information, bandwidth information, device position information and the like of PCI devices; byte space occupied by type data update of the SMBIOS protocol specification table after the DXE is started is calculated in advance and reserved;

and step S14, after all the information in the SMBIOS protocol specification table is updated, calculating SMIOS the total resource requirement of the protocol specification table and applying for the corresponding memory space.

When BIOS starts, BIOS updates the type data of SMBIOS protocol specification table in dynamic mode instead of static mode, and at the same time, during DXE phase, the data of SMBIOS protocol table types 0, 1, 2, 3,4, 12, 17, 18, 19, 20, 39, 41 are updated to the above type by IPMI protocol or BIOS self-acquired mode, if not during DXE phase, the reserved byte number is calculated by the maximum byte number sum required by each type under the system before, after DXE is finished and before entering into operating system, the data is updated to SMBIOS protocol before entering into operating system, and the occupied data is the maximum byte number of SMBIOS reserved before. The method has the advantages that the stage data of the original updated SMBIOS protocol specification table is kept unchanged in a dynamic mode, the maximum byte number actually required to be reserved is calculated in a maximized mode through the server configuration information after entering the operating system, and the maximum byte number is used before entering the system after the DXE stage is finished, so that the problem of downtime caused by randomly updating the type data of the SMBIOS protocol specification table can be solved, and the stability of the system is improved.

As an alternative implementation, fig. 5 is a lane diagram of an updated SMBIOS protocol specification table according to an embodiment of the present application, where, as shown in fig. 5, in the DEX stage, information of FRU is updated into types 0, 1,2, and 3, information of CPU vendor, CPU model, CPU rate, CPU core number, etc. is updated into type 4, physical silk-screen information (physical silk-screen information and interface information of a motherboard) is updated into type 12, memory information (memory number, memory slot silk-screen information, memory capacity, functional characteristic information supported by memory vendor, memory, and memory) is updated into types 17, 18, and 19, communication protocols of basic input/output system and baseboard management controller (communication protocols of BIOS and BMC) are updated into type 20, power supply information (information of power vendor, power supply delivery date, power supply bit information, power supply location information, etc.) is updated into type 39, on-board device information (on-board device and on-board storage medium of motherboard) is updated into type 41, and PCI interface information (slot information of PCI device, bandwidth information, device location information, etc. is updated into type 9; and in the OS phase, the total reserved resources of the above type are calculated.

From the description of the above embodiments, it will be clear to a person skilled in the art that the method according to the above embodiments may be implemented by means of software plus the necessary general hardware platform, but of course also by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present application.

In this embodiment, a device is further provided, and the device is used to implement the foregoing embodiments and preferred embodiments, which are not described in detail. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.

Fig. 6 is a block diagram of an information management apparatus of a server according to an embodiment of the present application, as shown in fig. 6, the apparatus including: an obtaining module 602, configured to determine, when a server is powered on or restarted, a type that needs to be dynamically updated in a protocol specification table as a target type, to obtain a target type set, where the type in the protocol specification table is used to record management information of the server; a determining module 604, configured to determine total reserved resources according to preset resources of each target type in the target type set, where the preset resources are resources that are preconfigured according to management information recorded by the target type; and an updating module 606, configured to update management information of each target type in the protocol specification table through the total reserved resources.

In an exemplary embodiment, the apparatus is further configured to determine, as a first target type, a type of management information related to the number of hardware recorded in the target type set, and obtain a first target type set; determining the type of the management information recorded in the target type set, which is irrelevant to the quantity of hardware, as a second target type, and obtaining a second target type set; determining the sum of preset resources of each type in the first target type set as a first preset resource sum, and determining the sum of preset resources of each type in the second target type set as a second preset resource sum; and determining the sum of the first preset resource sum and the second preset resource sum as the total reserved resource.

In an exemplary embodiment, the apparatus is further configured to obtain the total reserved resource by:

In an exemplary embodiment, the apparatus is further configured to determine, as the first target type, type 4, type 9, type 17, type 18, type 19, type 39 in the protocol specification table, where the type 4 is configured to record CPU information of a central processing unit of the server, the management information includes the CPU information, the number of pieces of hardware includes a number of CPUs in the server, the type 9 is configured to record peripheral component interconnect PCI interface information of the server, the number of pieces of hardware includes a number of PCIs in the server, the type 17, type 18, type 19 is configured to record memory information of the server, the number of pieces of hardware includes a number of memories in the server, the type 39 is configured to record power information of the server, and the number of pieces of hardware includes a number of power supplies in the server.

In an exemplary embodiment, the apparatus is further configured to determine a type 0, a type 1, a type 2, a type 3, a type 12, a type 20, and a type 41 in the protocol specification table as a second target type, where the type 0, the type 1, the type 2, and the type 3 are used to record field replaceable unit FRU information of the server, the type 12 is used to record physical silk screen information, the type 20 is used to record a communication protocol of a basic input output system and a baseboard management controller of the server, and the type 41 is used to record on-board device information of the server.

In an exemplary embodiment, the apparatus is further configured to update the total reserved resources into a BIOS image of a basic input output system and restart the server.

In an exemplary embodiment, the apparatus is further configured to obtain, after entering a DXE phase of the driver execution environment and before ending the DXE phase, current latest FRU information through a BIOS; and updating the current latest FRU information to the type 0, the type 1, the type 2 and the type 3 in the protocol specification table.

In an exemplary embodiment, the apparatus is further configured to obtain current latest CPU information, and update the latest CPU information to type 4, where the CPU information includes: CPU manufacturer, CPU model, CPU speed, CPU core number; after the update to the type 4 is determined, acquiring current latest physical silk-screen information, and updating the current latest physical silk-screen information to the type 12; after the update of the type 12 is determined, acquiring current latest memory information, and updating the memory information to the type 17, the type 18 and the type 19, wherein the memory information comprises the memory quantity, the memory slot silk screen information, the memory capacity, the memory manufacturer and the memory supported functional characteristics; after the update of the type 17, the type 18 and the type 19 is determined, the communication protocol of the latest basic input output system and the baseboard management controller is acquired, and the communication protocol of the latest basic input output system and the baseboard management controller is updated to the type 20.

In an exemplary embodiment, the apparatus is further configured to obtain the latest power information, and update the latest power information to type 39, where the power information includes: power supply manufacturer, power supply delivery date, power supply in-place information and power supply position information; after the update of the type 39 is determined, the latest on-board device information is acquired, and the latest on-board device information is updated to the type 41, wherein the on-board device information comprises the position information of an on-board storage medium.

In an exemplary embodiment, the apparatus is further configured to obtain latest peripheral component interconnect PCI interface information after the DXE phase ends and before entering an operating system; and updating the PCI interface information to the type 9.

In an exemplary embodiment, the apparatus is further configured to determine a total resource requirement of the protocol specification table and apply for a corresponding memory space after determining that the protocol specification table is updated.

It should be noted that each of the above modules may be implemented by software or hardware, and for the latter, it may be implemented by, but not limited to: the modules are all located in the same processor; or the above modules may be located in different processors in any combination.

Embodiments of the present application also provide a computer readable storage medium having a computer program stored therein, wherein the computer program is arranged to perform the steps of any of the method embodiments described above when run.

In one exemplary embodiment, the computer readable storage medium may include, but is not limited to: a usb disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory RAM), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing a computer program.

An embodiment of the application also provides an electronic device comprising a memory having stored therein a computer program and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.

In an exemplary embodiment, the electronic device may further include a transmission device connected to the processor, and an input/output device connected to the processor.

Embodiments of the application also provide a computer program product comprising a computer program which, when executed by a processor, implements the steps of any of the method embodiments described above.

Specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the exemplary implementation, and this embodiment is not described herein.

It will be appreciated by those skilled in the art that the modules or steps of the application described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may be implemented in program code executable by computing devices, so that they may be stored in a storage device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than that shown or described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps of them may be fabricated into a single integrated circuit module. Thus, the present application is not limited to any specific combination of hardware and software.

The above description is only of the preferred embodiments of the present application and is not intended to limit the present application, but various modifications and variations can be made to the present application by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the principle of the present application should be included in the protection scope of the present application.

Claims

1. An information management method of a server, comprising:

Under the condition that a server is electrified or restarted, determining the type needing to be dynamically updated in a protocol specification table as a target type to obtain a target type set, wherein the type in the protocol specification table is used for recording management information of the server;

Determining total reserved resources according to preset resources of each target type in the target type set, wherein the preset resources are resources which are preconfigured according to management information recorded by the target type;

Updating the management information of each target type in the protocol specification table through the total reserved resources;

Wherein determining the total reserved resource according to the preset resources of each target type in the target type set comprises:

determining the type of the management information recorded in the target type set and related to the hardware quantity as a first target type, and obtaining a first target type set;

determining the type of the management information recorded in the target type set, which is irrelevant to the quantity of hardware, as a second target type, and obtaining a second target type set;

determining the sum of preset resources of each type in the first target type set as a first preset resource sum, and determining the sum of preset resources of each type in the second target type set as a second preset resource sum;

and determining the sum of the first preset resource sum and the second preset resource sum as the total reserved resource.

2. The method of claim 1, wherein determining the sum of the reserved resources of the first set of target types and the reserved resources of the second target as the total reserved resources comprises:

The total reserved resources are obtained by the following formula:

,

wherein T is the total reserved resource, Is the hardware quantity of the ith target type in the first set of target types, N, M is an integer greater than or equal to 1,Is a preset resource of the i-th target type,Is a preset resource of the jth target type in the second target type set.

3. The method according to claim 1, wherein determining the type of the management information recorded in the target type set and related to the number of hardware as the first target type, to obtain the first target type set, includes:

Determining type 4, type 9, type 17, type 18, type 19 and type 39 in the protocol specification table as the first target type, wherein the type 4 is used for recording CPU information of a central processing unit of the server, the management information comprises the CPU information, the hardware quantity comprises the quantity of CPUs in the server, the type 9 is used for recording PCI interface information of peripheral components of the server, the hardware quantity comprises the quantity of PCI in the server, the type 17, type 18 and type 19 are used for recording memory information of the server, the hardware quantity comprises the quantity of memory in the server, the type 39 is used for recording power supply information of the server, and the hardware quantity comprises the quantity of power supplies in the server.

4. The method according to claim 1, wherein determining the type of the management information recorded in the target type set, which is irrelevant to the amount of hardware, as the second target type, and obtaining the second target type set includes:

And determining the type 0, the type 1, the type 2, the type 3, the type 12, the type 20 and the type 41 in the protocol specification table as a second target type, wherein the type 0, the type 1, the type 2 and the type 3 are used for recording Field Replaceable Unit (FRU) information of the server, the type 12 is used for recording physical silk-screen information, the type 20 is used for recording a communication protocol of a basic input and output system and a baseboard management controller of the server, and the type 41 is used for recording on-board equipment information of the server.

5. The method according to any one of claims 1 to 4, wherein after said determining total reserved resources from preset resources of each of said target types in said set of target types, the method further comprises:

And updating the total reserved resources into a Basic Input Output System (BIOS) mirror image and restarting the server.

6. The method of claim 5, wherein updating the management information for each of the target types in the protocol specification table after restarting the server comprises:

after entering a DXE phase of a driver execution environment and before ending the DXE phase, acquiring current latest FRU information through a basic input output system BIOS;

And updating the current latest FRU information to the type 0, the type 1, the type 2 and the type 3 in the protocol specification table.

7. The method of claim 6, wherein upon determining that the type 0, type 1, type 2, type 3 are updated, the method further comprises:

Acquiring current latest Central Processing Unit (CPU) information, and updating the latest CPU information to a type 4, wherein the CPU information comprises: CPU manufacturer, CPU model, CPU speed, CPU core number;

after the update to the type 4 is determined, acquiring current latest physical silk-screen information, and updating the current latest physical silk-screen information to the type 12;

after the update of the type 12 is determined, acquiring current latest memory information, and updating the memory information to the type 17, the type 18 and the type 19, wherein the memory information comprises the memory quantity, the memory slot silk screen information, the memory capacity, the memory manufacturer and the memory supported functional characteristics;

after the update of the type 17, the type 18 and the type 19 is determined, the communication protocol of the latest basic input output system and the baseboard management controller is acquired, and the communication protocol of the latest basic input output system and the baseboard management controller is updated to the type 20.

8. The method of claim 7, wherein upon determining that the type 20 is updated, the method further comprises:

acquiring the latest power supply information and updating the latest power supply information to a type 39, wherein the power supply information comprises: power supply manufacturer, power supply delivery date, power supply in-place information and power supply position information;

After the update of the type 39 is determined, the latest on-board device information is acquired, and the latest on-board device information is updated to the type 41, wherein the on-board device information comprises the position information of an on-board storage medium.

9. The method of claim 8, wherein upon determining that the type 41 is updated, the method further comprises:

after the DXE phase is finished and before the DXE phase enters an operating system, the latest PCI interface information of the peripheral component interconnection is obtained;

and updating the PCI interface information to the type 9.

10. The method of claim 1, wherein after updating the management information of each of the target types in the protocol specification table by the total reserved resources, the method further comprises:

After the protocol specification table is updated, determining the total resource requirement of the protocol specification table and applying for a corresponding memory space.

11. An information management apparatus of a server, comprising:

The system comprises an acquisition module, a storage module and a control module, wherein the acquisition module is used for determining the type which needs to be dynamically updated in a protocol specification table as a target type under the condition that a server is powered on or restarted to obtain a target type set, wherein the type in the protocol specification table is used for recording management information of the server;

The determining module is used for determining total reserved resources according to preset resources of each target type in the target type set, wherein the preset resources are resources which are preconfigured according to management information recorded by the target type;

The updating module is used for updating the management information of each target type in the protocol specification table through the total reserved resources;

The device is also used for determining the type of the management information and the hardware quantity related recorded in the target type set as a first target type to obtain a first target type set; determining the type of the management information recorded in the target type set, which is irrelevant to the quantity of hardware, as a second target type, and obtaining a second target type set; determining the sum of preset resources of each type in the first target type set as a first preset resource sum, and determining the sum of preset resources of each type in the second target type set as a second preset resource sum; and determining the sum of the first preset resource sum and the second preset resource sum as the total reserved resource.

12. A computer-readable storage medium comprising,

The computer readable storage medium has stored therein a computer program, wherein the computer program when executed by a processor realizes the steps of the method as claimed in any of claims 1 to 10.

13. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that,

The processor, when executing the computer program, implements the steps of the method as claimed in any one of claims 1 to 10.

14. A computer program product comprising a computer program, characterized in that,

The computer program implementing the steps of the method of any one of claims 1 to 10 when executed by a processor.