Pfr anomaly recovery bmc capability test method, computer device, and storage medium

Abstract

The application provides a PFR abnormality recovery BMC capability test method, computer equipment and a storage medium, the method tests starting, and a test firmware environment is configured; a PfrInfoApp is configured through a U disk or a port; a PFR register state is checked through an instruction, whether PFR has been started is judged, if not, PFR is started through an instruction under Shll, and is restarted, the PFR register state is checked again through an instruction; if yes, the server is restarted after power failure, test firmware is uploaded through a BMC, the server is powered off when entering a T-1 period, is powered on after waiting for 1 min, and the PFR register and the PFR state under the BMC are checked. The automation of BMC recovery capability test under the abnormality of PFR system is realized, the time loss of manual test environment construction and cycle test is reduced, the test result can be automatically analyzed according to the required standard of the project, the test file is automatically generated, the workload of personnel is reduced, and the test situation can also be more accurate and detailed.

Description

Technical Field

[0001] This invention relates to the field of chip technology, specifically to a method for testing BMC capability recovery from PFR anomalies, a computer device, and a storage medium, and more particularly to a method for testing the BMC firmware refresh anomaly recovery capability of a server with PFR functionality, a computer device, and a storage medium. Background Technology

[0002] The BMC firmware in a server is a crucial component for server management and interaction functions, and its stable operation directly impacts the overall stability of the server. Therefore, servers are typically configured with PFR (Platform Firmware Resilience) to ensure the proper functioning of the BMC firmware. PFR protects the server firmware in the event of firmware anomalies by automatically updating the erroneous firmware to a pre-stored version. The timely and effective operation of PFR is a critical factor in ensuring server operational security. Therefore, server testing phases require testing the functionality, stability, and handling of anomalies related to PFR. Currently, server firmware upgrades are typically performed remotely via the BMC web interface. This involves burning the firmware program into the BMC chip, which then burns the firmware program into flash memory while the BMC is powered on. This upgrade method requires the machine to be constantly powered on; any abnormal power outage during the upgrade process can lead to BMC program corruption or even crashes.

[0003] In the current technological environment, testers can confirm the required testing environment, tools, testing methods, and test data requirements by consulting PFR technical documentation, and configure the testing environment according to the documentation. They then manually install the corresponding testing software, drivers, and other software, and configure the operating system environment. Afterwards, they manually trigger abnormal situations according to the testing requirements and collect corresponding test data for analysis. To address the high level of specialization and complex tools involved in PFR testing, a functional integration approach can be adopted. For example, CN202110964736.0 can provide functions such as checking PFR function support, verifying the compatibility of the PFR firmware version, and querying PFR test register data, reducing workload and improving efficiency.

[0004] The aforementioned solutions can facilitate information collection and software management during PFR testing, simplifying the testing process and improving efficiency to some extent. However, existing solutions are not suitable for the actual situation of PFR testing. They cannot automatically test the disaster recovery capabilities of the server BMC, which is the most crucial aspect of PFR, nor can they perform stability testing on PFR functional components. Testers still lack a clear testing procedure, making accurate, reproducible, and reliable testing of the BMC firmware capabilities impossible. Summary of the Invention

[0005] In view of this, the purpose of this invention is to provide a test method, computer equipment and storage medium for server BMC firmware refresh anomaly recovery capability with PFR function, which simplifies the steps of PFR recovery function test when BMC refresh is abnormal, can realize the function of testing BMC firmware recovery capability with PFR disaster recovery function, meets all the requirements of test data, environment and steps, and improves test efficiency.

[0006] To achieve the above objectives, in one respect, the present invention provides a method for testing the PFR anomaly recovery BMC capability, the method comprising:

[0007] Start the test and configure the test firmware environment; configure PfrInfoApp via USB flash drive or port.

[0008] The PFR register status is checked by the command to determine whether PFR is enabled. If not, PFR is enabled by the command Shll and then restarted. The PFR register status is checked again by the command.

[0009] If so, the server is powered off and restarted. The test firmware is uploaded through the BMC. The server is powered off when it enters the T-1 period, and powered on again after 1 minute. The PFR register and the PFR status under the BMC are checked.

[0010] As a further aspect of the present invention, before the test starts, the server performs a power-on self-test and modifies the BIOS settings as follows:

[0011] In the BIOS setup interface, go to Platform Configuration -> Miscellaneous Configuration -> PFR Provision and set it to Enable. Press F10 to save and exit.

[0012] As a further aspect of the present invention, configuring PfrInfoApp via USB flash drive or port includes: booting the PfrInfoApp tool into the server Shell environment via USB flash drive or other media or port; when installed via USB flash drive, test data and operation records will automatically generate corresponding logs according to the date; when booted via port, relevant data will be automatically sent to the receiving storage device.

[0013] As a further aspect of the present invention, the PFR abnormal recovery BMC capability testing method further includes: restarting the machine and booting into the UEFI Shell interface;

[0014] In the UEFI shell interface, navigate to the path of the PfrInfoApp tool and run the command PfrInfoApp.efi -s. After the command is executed, a log file named with the date will be automatically generated in the tool's path.

[0015] As a further aspect of the present invention, executing this instruction will check the status flags of the PFR to confirm the working status of the PFR. In this test, the test data is as follows:

[0016] A Platform State of 0x01, a UFM Status of 0x20, and a UFM Provisioned Bit of 0x01 indicate that the PFR function is enabled. A Platform State of 0x09, a UFM Status of 0x00, and a UFM Provisioned Bit of 0x00 indicate that the PFR function is not enabled.

[0017] As a further aspect of the present invention, for servers where PFR is not enabled, the function is manually enabled using the command Pfrconfig-P, and the server power is manually cut off when the prompt ends to complete the command refresh; the hpm file of the BMC firmware program is uploaded to the firmware update interface of the BMC web interface to boot the firmware required for BMC upgrade and refresh into the internal storage space of BMC.

[0018] As a further aspect of the present invention, after the firmware update task bar displays COMPLETE 100%, the machine will automatically restart and enter the T-1 stage after about 1 minute. In the T-1 stage, the server is burning the previously uploaded BMC firmware information onto the BMC chip via PFR, and is in the middle stage of modifying the chip storage. After entering the T-1 stage for a period of time, the power is manually cut off to create an abnormal situation, and the machine is powered on again after 1 minute. In the T-1 stage, PFR is burning the BMC chip, the old firmware has been refreshed and deleted, and the new firmware has not yet been refreshed.

[0019] As a further aspect of the present invention, after power-on, the machine boots into the UEFI shell interface, and the log automatically generated after running the PfrInfoApp.efi-s command is compared with the log in the UEFI shell interface after restarting the machine. The BMC firmware displayed in the BMC interface is checked to see if it has been restored to the predetermined firmware. The machine is then restarted to enter the BIOS interface to check if the PFR status is still enabled.

[0020] In another aspect, the present invention provides a computer device including a memory and a processor, wherein the memory stores a computer program, which, when executed by the processor, performs any of the above-described PFR anomaly recovery BMC capability testing methods according to the present invention.

[0021] In another aspect, the present invention provides a computer-readable storage medium storing computer program instructions that, when executed, implement any of the above-described PFR anomaly recovery BMC capability testing methods according to the present invention.

[0022] Compared to traditional implementations, the main advantages of this invention are:

[0023] The PFR anomaly recovery BMC capability testing method, computer equipment, and storage medium of this invention automate the BMC recovery capability testing under PFR system anomaly conditions, reducing the time lost in manual test environment setup and iterative testing. The fully automated testing process improves the accuracy and rigor of the tests. It can automatically analyze test results according to the standards required by the project and automatically generate test files, reducing manual workload while providing a more accurate and detailed reflection of the test situation.

[0024] These or other aspects of this application will become more apparent from the following description of embodiments. It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only, and are not intended to limit the scope of this application. Attached Figure Description

[0025] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other embodiments can be obtained based on these drawings without creative effort.

[0026] In the diagram:

[0027] Figure 1 This is a flowchart of the task management and data scheduling process of the PFR anomaly recovery BMC capability testing system of the present invention;

[0028] Figure 2 This is a schematic diagram of an embodiment of a computer-readable storage medium for implementing the PFR anomaly recovery BMC capability testing method of the present invention;

[0029] Figure 3 This is a schematic diagram of the hardware structure of a computer device for implementing the PFR anomaly recovery BMC capability testing method of the present invention. Detailed Implementation

[0030] To make the objectives, technical solutions, and advantages of the present invention clearer, the embodiments of the present invention will be further described in detail below with reference to specific examples and the accompanying drawings.

[0031] It should be noted that all uses of "first" and "second" in the embodiments of the present invention are for the purpose of distinguishing two different entities or different parameters with the same name. Therefore, "first" and "second" are merely for convenience of expression and should not be construed as limiting the embodiments of the present invention. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, such as other steps or units inherent in a process, method, system, product, or device that includes a series of steps or units.

[0032] To make the objectives, technical solutions, and advantages of this invention clearer, the embodiments of this invention will be further described in detail below with reference to specific examples and the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative and are not intended to limit this application.

[0033] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0034] The flowchart shown in the attached diagram is for illustrative purposes only and does not necessarily include all content and operations / steps, nor does it necessarily have to be performed in the order described. For example, some operations / steps can be broken down, combined, or partially merged, so the actual execution order may change depending on the actual situation.

[0035] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0036] Because existing technical solutions are not suitable for the actual situation of PFR testing, they cannot automatically test the disaster recovery capability of the server BMC, which is the most important aspect of PFR, nor can they perform stability testing on PFR functional components. Testers still lack a clear testing procedure, making it impossible to achieve accurate, reproducible, and reliable testing of this BMC firmware capability.

[0037] In view of this, embodiments of the present invention provide a PFR anomaly recovery BMC capability testing method, computer equipment, and storage medium, which simplifies the steps of PFR recovery function testing when BMC refresh anomaly occurs, can realize the function of testing BMC firmware recovery capability of PFR disaster recovery function, meet all the requirements of test data, environment, and steps, and improve test efficiency.

[0038] In some embodiments of the present invention, a method for testing the BMC capability to recover from PFR anomalies is provided as a method for testing the BMC firmware refresh anomaly recovery capability of a server with PFR function. This method can be roughly divided into several parts when testing the BMC capability to recover from PFR anomalies:

[0039] 1. Configure the test environment 2. Import test software and firmware 3. Set test parameter requirements and test methods 4. Guide PFR to refresh BMC 5. Actively create abnormal situations to simulate BMC crash 6. Check PFR's BMC recovery status 7. Collect, statistically analyze, and analyze test results 8. Perform loop tests to verify functional stability 9. Output test report.

[0040] Specifically, in the embodiments of the present invention, see... Figure 1 As shown, a method for testing PFR anomaly recovery BMC capability is provided, the method including:

[0041] Start the test and configure the test firmware environment; configure PfrInfoApp via USB flash drive or port.

[0042] The PFR register status is checked by the command to determine whether PFR is enabled. If not, PFR is enabled by the command Shll and then restarted. The PFR register status is checked again by the command.

[0043] If so, the server is powered off and restarted. The test firmware is uploaded through the BMC. The server is powered off when it enters the T-1 period, and powered on again after 1 minute. The PFR register and the PFR status under the BMC are checked.

[0044] In embodiments of this invention, the firmware for the test-specific BMC and BIOS is updated according to the actual needs of the project. This firmware can be generated by adding PFR testing functionality to the original server firmware based on the actual project situation. The specific steps are as follows:

[0045] Step 1: Perform a power-on self-test on the server and modify the BIOS settings as follows:

[0046] In the BIOS setup interface, go to Platform Configuration -> Miscellaneous Configuration -> PFR Provision option and set it to Enable. Press F10 to save and exit.

[0047] This step enables the PFR function in the BIOS, completing the subsequent preparations. For specific project requirements, the function can also be enabled or disabled by differentiating between PFR and non-PFR versions in the BIOS.

[0048] Step 2: Boot the PfrInfoApp tool into the server shell environment via USB flash drive or other media and port. When installed via USB flash drive, test data and operation records will be automatically generated into corresponding logs according to the date; when booting via port, relevant data will be automatically sent to the receiving storage device.

[0049] Step 3: Reboot the machine and boot into the UEFI Shell interface:

[0050] In the UEFI shell interface, navigate to the path of the PfrInfoApp tool and run the command PfrInfoApp.efi -s. After the command is executed, a log file named with the date will be automatically generated in the tool's path.

[0051] Executing this command will check the status flags of the PFR to confirm its working status. The test data of interest in this test are as follows:

[0052] A Platform State of 0x01, a UFM Status of 0x20, and a UFM Provisioned Bit of 0x01 indicate that the PFR function is enabled. A Platform State of 0x09, a UFM Status of 0x00, and a UFM Provisioned Bit of 0x00 indicate that the PFR function is not enabled.

[0053] Step 4: For servers where PFR is not enabled, you can manually enable the function using the command Pfrconfig -P, and manually disconnect the server power when prompted to finish (the software will display "pleas AC" when it finishes running) to complete the command refresh.

[0054] Step 5: Upload the hpm file of the BMC firmware program to the firmware update interface of the BMC web interface, and boot the firmware required for BMC upgrade and flashing into the internal storage space of BMC.

[0055] Step 6: After the firmware update task bar displays COMPLETE 100%, the machine will automatically restart and enter the T-1 stage after about 1 minute (the T-1 stage means that the machine power button is orange and the BMC heartbeat indicator light is off). The server in the T-1 stage is burning the BMC firmware information that was just uploaded onto the BMC chip via PFR, and is in the middle stage of modifying the chip's storage.

[0056] Step 7: After entering the T-1 stage for a period of time, manually cut off the power to create an abnormal situation, wait for 1 minute, and then power on the machine.

[0057] During the T-1 phase, PFR is programming the BMC chip. The old firmware has been refreshed and deleted, and the new firmware has not yet been refreshed. If the server is powered off at this time, the BMC chip will be in an abnormal state where it cannot work, simulating a situation where the BMC firmware malfunctions and loses functionality during server operation.

[0058] Waiting for 1 minute is to allow all the capacitors on the motherboard to discharge completely, so as to avoid insufficient power-down of the firmware due to too rapid power restoration, which could lead to experimental errors.

[0059] Step 8: After powering on, boot the machine into the UEFI shell interface, and compare the automatically generated log after running the PfrInfoApp.efi-s command with the log in step 3.

[0060] After the server powers on, PFR will automatically check the server's BMC firmware status. For corrupted or malfunctioning firmware, it will refresh the corresponding firmware version after power-on to restore functionality. This refreshed firmware can be a specific version embedded within PFR, or it can be version data from the backup chip in multi-chip disaster recovery mode.

[0061] Step 9: Check if the BMC firmware displayed on the BMC interface has been restored to the predetermined firmware. Restart and enter the BIOS interface to check if the PFR status is still enabled.

[0062] Step 10: Repeat the above steps to verify the stability of PFR operation.

[0063] The PFR anomaly recovery BMC capability testing method of this invention automates the testing of BMC recovery capability under PFR system anomalies, reducing the time lost in manual test environment setup and iterative testing. The fully automated testing process improves the accuracy and rigor of the tests. It can automatically analyze test results according to the standards required by the project and automatically generate test files, reducing manual workload while providing a more accurate and detailed reflection of the test situation.

[0064] It should be understood that although the above description follows a certain order, these steps are not necessarily executed in that order. Unless otherwise expressly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, some steps in this embodiment may include multiple steps or multiple stages, which are not necessarily completed at the same time, but may be executed at different times. The execution order of these steps or stages is not necessarily sequential, but may be performed alternately or in turn with other steps or at least a portion of the steps or stages in other steps.

[0065] In a second aspect, an embodiment of the present invention also provides a computer device 400, including a memory 420 and a processor 410. The memory stores a computer program, which, when executed by the processor, implements the method of any of the above embodiments, including the following steps:

[0066] Step 1: Perform a power-on self-test on the server and modify the BIOS settings as follows:

[0067] In the BIOS setup interface, go to Platform Configuration -> Miscellaneous Configuration -> PFR Provision option and set it to Enable. Press F10 to save and exit.

[0068] This step enables the PFR function in the BIOS, completing the subsequent preparations. For specific project requirements, the function can also be enabled or disabled by differentiating between PFR and non-PFR versions in the BIOS.

[0069] Step 2: Boot the PfrInfoApp tool into the server shell environment via USB flash drive or other media and port. When installed via USB flash drive, test data and operation records will be automatically generated into corresponding logs according to the date; when booting via port, relevant data will be automatically sent to the receiving storage device.

[0070] Step 3: Reboot the machine and boot into the UEFI Shell interface:

[0071] In the UEFI shell interface, navigate to the path of the PfrInfoApp tool and run the command PfrInfoApp.efi -s. After the command is executed, a log file named with the date will be automatically generated in the tool's path.

[0072] Executing this command will check the status flags of the PFR to confirm its working status. The test data of interest in this test are as follows:

[0073] A Platform State of 0x01, a UFM Status of 0x20, and a UFM Provisioned Bit of 0x01 indicate that the PFR function is enabled. A Platform State of 0x09, a UFM Status of 0x00, and a UFM Provisioned Bit of 0x00 indicate that the PFR function is not enabled.

[0074] Step 4: For servers where PFR is not enabled, you can manually enable the function using the command Pfrconfig -P, and manually disconnect the server power when prompted to finish (the software will display "pleas AC" when it finishes running) to complete the command refresh.

[0075] Step 5: Upload the hpm file of the BMC firmware program to the firmware update interface of the BMC web interface, and boot the firmware required for BMC upgrade and flashing into the internal storage space of BMC.

[0076] Step 6: After the firmware update task bar displays COMPLETE 100%, the machine will automatically restart and enter the T-1 stage after about 1 minute (the T-1 stage means that the machine power button is orange and the BMC heartbeat indicator light is off). The server in the T-1 stage is burning the BMC firmware information that was just uploaded onto the BMC chip via PFR, and is in the middle stage of modifying the chip's storage.

[0077] Step 7: After entering the T-1 stage for a period of time, manually cut off the power to create an abnormal situation, wait for 1 minute, and then power on the machine.

[0078] During the T-1 phase, PFR is programming the BMC chip. The old firmware has been refreshed and deleted, and the new firmware has not yet been refreshed. If the server is powered off at this time, the BMC chip will be in an abnormal state where it cannot work, simulating a situation where the BMC firmware malfunctions and loses functionality during server operation.

[0079] Waiting for 1 minute is to allow all the capacitors on the motherboard to discharge completely, so as to avoid insufficient power-down of the firmware due to too rapid power restoration, which could lead to experimental errors.

[0080] Step 8: After powering on, boot the machine into the UEFI shell interface, and compare the automatically generated log after running the PfrInfoApp.efi-s command with the log in step 3.

[0081] After the server powers on, PFR will automatically check the server's BMC firmware status. For corrupted or malfunctioning firmware, it will refresh the corresponding firmware version after power-on to restore functionality. This refreshed firmware can be a specific version embedded within PFR, or it can be version data from the backup chip in multi-chip disaster recovery mode.

[0082] Step 9: Check if the BMC firmware displayed on the BMC interface has been restored to the predetermined firmware. Restart and enter the BIOS interface to check if the PFR status is still enabled.

[0083] Step 10: Repeat the above steps to verify the stability of PFR operation.

[0084] like Figure 3 The diagram shown is a hardware structure schematic of an embodiment of the computer device for performing the PFR anomaly recovery BMC capability testing method provided by the present invention. Figure 3 Taking the computer device 400 shown as an example, this computer device includes a processor 410 and a memory 420, and may also include an input device 430 and an output device 440. The processor 410, memory 420, input device 430, and output device 440 can be connected via a bus or other means. Figure 3 Taking a bus connection as an example, input device 430 can receive input digital or character information and generate signal inputs related to the PFR abnormal recovery BMC capability test. Output device 440 may include display devices such as a display screen.

[0085] Memory 420, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as the program instructions / modules corresponding to the PFR anomaly recovery BMC capability testing method in this embodiment. Memory 420 may include a program storage area and a data storage area, wherein the program storage area may store the operating system and application programs required for at least one function; the data storage area may store data created by using the PFR anomaly recovery BMC capability testing method, etc. In addition, memory 420 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, memory 420 may optionally include memory remotely located relative to processor 410, and these remote memories can be connected to the local module via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0086] Processor 410 executes various server functions and data processing by running non-volatile software programs, instructions, and modules stored in memory 420, thereby implementing the PFR anomaly recovery BMC capability testing method of the above method embodiment. The steps are as follows:

[0087] Step 1: Perform a power-on self-test on the server and modify the BIOS settings as follows:

[0088] In the BIOS setup interface, go to Platform Configuration -> Miscellaneous Configuration -> PFR Provision option and set it to Enable. Press F10 to save and exit.

[0089] This step enables the PFR function in the BIOS, completing the subsequent preparations. For specific project requirements, the function can also be enabled or disabled by differentiating between PFR and non-PFR versions in the BIOS.

[0090] Step 2: Boot the PfrInfoApp tool into the server shell environment via USB flash drive or other media and port. When installed via USB flash drive, test data and operation records will be automatically generated into corresponding logs according to the date; when booting via port, relevant data will be automatically sent to the receiving storage device.

[0091] Step 3: Reboot the machine and boot into the UEFI Shell interface:

[0092] In the UEFI shell interface, navigate to the path of the PfrInfoApp tool and run the command PfrInfoApp.efi -s. After the command is executed, a log file named with the date will be automatically generated in the tool's path.

[0093] Executing this command will check the status flags of the PFR to confirm its working status. The test data of interest in this test are as follows:

[0094] A Platform State of 0x01, a UFM Status of 0x20, and a UFM Provisioned Bit of 0x01 indicate that the PFR function is enabled. A Platform State of 0x09, a UFM Status of 0x00, and a UFM Provisioned Bit of 0x00 indicate that the PFR function is not enabled.

[0095] Step 4: For servers where PFR is not enabled, you can manually enable the function using the command Pfrconfig -P, and manually disconnect the server power when prompted to finish (the software will display "pleas AC" when it finishes running) to complete the command refresh.

[0096] Step 5: Upload the hpm file of the BMC firmware program to the firmware update interface of the BMC web interface, and boot the firmware required for BMC upgrade and flashing into the internal storage space of BMC.

[0097] Step 6: After the firmware update task bar displays COMPLETE 100%, the machine will automatically restart and enter the T-1 stage after about 1 minute (the T-1 stage means that the machine power button is orange and the BMC heartbeat indicator light is off). The server in the T-1 stage is burning the BMC firmware information that was just uploaded onto the BMC chip via PFR, and is in the middle stage of modifying the chip's storage.

[0098] Step 7: After entering the T-1 stage for a period of time, manually cut off the power to create an abnormal situation, wait for 1 minute, and then power on the machine.

[0099] During the T-1 phase, PFR is programming the BMC chip. The old firmware has been refreshed and deleted, and the new firmware has not yet been refreshed. If the server is powered off at this time, the BMC chip will be in an abnormal state where it cannot work, simulating a situation where the BMC firmware malfunctions and loses functionality during server operation.

[0100] Waiting for 1 minute is to allow all the capacitors on the motherboard to discharge completely, so as to avoid insufficient power-down of the firmware due to too rapid power restoration, which could lead to experimental errors.

[0101] Step 8: After powering on, boot the machine into the UEFI shell interface, and compare the automatically generated log after running the PfrInfoApp.efi-s command with the log in step 3.

[0102] After the server powers on, PFR will automatically check the server's BMC firmware status. For corrupted or malfunctioning firmware, it will refresh the corresponding firmware version after power-on to restore functionality. This refreshed firmware can be a specific version embedded within PFR, or it can be version data from the backup chip in multi-chip disaster recovery mode.

[0103] Step 9: Check if the BMC firmware displayed on the BMC interface has been restored to the predetermined firmware. Restart and enter the BIOS interface to check if the PFR status is still enabled.

[0104] Step 10: Repeat the above steps to verify the stability of PFR operation.

[0105] It should be understood that, where there is no conflict, all the embodiments, features and advantages described above for the PFR anomaly recovery BMC capability testing method according to the present invention are equally applicable to the PFR anomaly recovery BMC capability testing system and storage medium according to the present invention.

[0106] Finally, it should be noted that the computer-readable storage medium (e.g., memory) described herein can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. By way of example, and not limitation, non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM), which can act as external cache memory. By way of example, and not limitation, RAM can be obtained in various forms, such as synchronous RAM (DRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct Rambus RAM (DRRAM). The storage devices disclosed herein are intended to include, but are not limited to, these and other suitable types of memory.

[0107] The PFR anomaly recovery BMC capability testing method, computer equipment, and storage medium of this invention automate the BMC recovery capability testing under PFR system anomaly conditions, reducing the time lost in manual test environment setup and iterative testing. The fully automated testing process improves the accuracy and rigor of the tests. It can automatically analyze test results according to the standards required by the project and automatically generate test files, reducing manual workload while providing a more accurate and detailed reflection of the test situation.

[0108] The above are exemplary embodiments disclosed in this invention. However, it should be noted that various changes and modifications can be made without departing from the scope of the embodiments of this invention as defined by the claims. The functions, steps, and / or actions of the methods according to the disclosed embodiments described herein do not need to be performed in any particular order. Furthermore, although the elements disclosed in the embodiments of this invention may be described or claimed individually, they may be understood as multiple unless explicitly limited to a singular number.

[0109] It should be understood that, as used herein, the singular form "a" is intended to include the plural form as well, unless the context clearly supports an exception. It should also be understood that, as used herein, "and / or" refers to any and all possible combinations of one or more of the associatedly listed items. The embodiment numbers disclosed above are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0110] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of the invention (including the claims) is limited to these examples. Within the framework of the invention, technical features of the above embodiments or different embodiments can be combined, and many other variations of different aspects of the invention exist, which are not provided in the details for the sake of brevity. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the invention should be included within the protection scope of the invention.

Claims

1. A method for testing the ability of PFR to recover from abnormal BMC, characterized in that, The method includes; Start the test and configure the test firmware environment; configure PfrInfoApp via USB flash drive or port. Check the PFR register status using commands to determine if PFR is enabled. If not, enable PFR using Shell commands and restart. Then check the PFR register status again using commands. If so, the server will power off and restart, and upload the test firmware via BMC. After the firmware update task bar displays COMPLETE 100%, the machine will automatically restart and enter the T-1 stage after 1 minute. In the T-1 stage, the server is burning the previously uploaded BMC firmware information onto the BMC chip via PFR, which is in the middle stage of modifying the chip's storage. After entering the T-1 stage for a period of time, manually cut off the power to create an abnormal situation, wait 1 minute, and then power on the machine. In the T-1 stage, PFR is burning the BMC chip, the old firmware has been refreshed and deleted, and the new firmware has not yet been refreshed. After powering on, boot the machine into the UEFI shell interface. Compare the log automatically generated after running the command PfrInfoApp.efi -s with the log generated after restarting the machine and booting into the UEFI shell interface. Check whether the BMC firmware displayed in the BMC interface has been restored to the predetermined firmware. Reboot into the BIOS interface and check whether the PFR status is still enabled.

2. The PFR anomaly recovery BMC capability testing method according to claim 1, characterized in that, Before starting the test, the server performs a power-on self-test and modifies the BIOS settings as follows: In the BIOS setup interface, go to Platform Configuration -> Miscellaneous Configuration -> PFRProvision and set it to Enable. Save the settings and exit the interface.

3. The PFR anomaly recovery BMC capability testing method according to claim 2, characterized in that, When configuring PfrInfoApp via USB flash drive or port, including: booting the PfrInfoApp tool into the server shell environment via USB flash drive or other media or port, test data and operation records will be automatically generated into corresponding logs according to the date when installed via USB flash drive; when booting via port, relevant data will be automatically sent to the receiving storage device.

4. The PFR anomaly recovery BMC capability testing method according to claim 2, characterized in that, The PFR abnormal recovery BMC capability test method also includes: restarting the machine and booting into the UEFI Shell interface; In the UEFI shell interface, navigate to the path of the PfrInfoApp tool and run the command PfrInfoApp.efi -s. After the command is executed, a log file named with the date will be automatically generated in the tool's path.

5. The PFR anomaly recovery BMC capability testing method according to claim 4, characterized in that, Executing this command will check the status flags of the PFR to confirm its working status. The test data in this example is as follows: A Platform State of 0x01, a UFM Status of 0x20, and a UFM Provisioned Bit of 0x01 indicate that the PFR function is enabled. A Platform State of 0x09, a UFM Status of 0x00, and a UFM Provisioned Bit of 0x00 indicate that the PFR function is not enabled.

6. The PFR anomaly recovery BMC capability testing method according to claim 5, characterized in that, For servers where PFR is not enabled, manually enable the function using the command Pfrconfig -P, and manually disconnect the server power when the prompt ends to complete the command refresh; upload the hpm file of the BMC firmware program in the firmware update interface of the BMC web interface to boot the firmware required for BMC upgrade and refresh into the internal storage space of BMC.

7. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the computer program is executed by the processor, it performs the PFR anomaly recovery BMC capability test method according to any one of claims 1-6.

8. A computer-readable storage medium storing computer program instructions, characterized in that, When the computer program instructions are executed, they implement the PFR anomaly recovery BMC capability test method according to any one of claims 1-6.

Images