CN116954666A

CN116954666A - Firmware refreshing method and device of array card, storage medium and electronic equipment

Info

Publication number: CN116954666A
Application number: CN202310953874.8A
Authority: CN
Inventors: 杨紫鑫
Original assignee: Suzhou Inspur Intelligent Technology Co Ltd
Current assignee: Suzhou Inspur Intelligent Technology Co Ltd
Priority date: 2023-07-31
Filing date: 2023-07-31
Publication date: 2023-10-27

Abstract

The embodiment of the application provides a firmware refreshing method and device of an array card, a storage medium and electronic equipment, wherein the method comprises the following steps: acquiring a firmware refreshing instruction, wherein the firmware refreshing instruction is used for indicating to refresh firmware of a designated array card on designated equipment; responding to the acquired firmware refreshing instruction, executing communication stopping operation, wherein the communication stopping operation is used for stopping interaction between the appointed array card and a group of target modules on the appointed equipment so as to enable a group of configuration files corresponding to the appointed array card to be in a refreshing permission state; after the communication stopping operation is executed, refreshing the firmware of the specified array card by using the specified refreshing file so as to refresh the firmware of the specified array card to a version corresponding to the specified refreshing file; the application can improve the refreshing efficiency of the array card firmware.

Description

Firmware refreshing method and device of array card, storage medium and electronic equipment

Technical Field

The embodiment of the application relates to the technical field of servers, in particular to a firmware refreshing method and device of an array card, a storage medium and electronic equipment.

Background

Hardware devices (e.g., servers applied to storage scenarios) typically need to be managed with an array card, and when the hardware devices are tested in batches, the array card firmware of the hardware devices needs to be refreshed, so that the versions of the array card firmware of the hardware devices in the same batch are unified.

In the related art, when the automatic test is performed on the hardware device, the array card firmware of the hardware device cannot be thoroughly refreshed in the operating system of the hardware device, so that the configuration file of the array card firmware remains, the refreshing of the array card firmware is incomplete, and the array card abnormality is caused.

Therefore, the firmware refreshing method of the array card in the related art has the technical problem of abnormal firmware refreshing of the array card.

Disclosure of Invention

The embodiment of the application provides a firmware refreshing method and device of an array card, a storage medium and electronic equipment, which at least solve the technical problem that the firmware refreshing method of the array card in the related technology has abnormal firmware refreshing of the array card.

According to one embodiment of the present application, there is provided a firmware refreshing method of an array card, including: acquiring a firmware refreshing instruction, wherein the firmware refreshing instruction is used for indicating to refresh firmware of a designated array card on designated equipment; responding to the acquired firmware refreshing instruction, and executing a communication stopping operation, wherein the communication stopping operation is used for stopping interaction between the appointed array card and a group of target modules on the appointed equipment so as to enable a group of configuration files corresponding to the appointed array card to be in a refreshing permission state; after the communication stopping operation is executed, the firmware of the appointed array card is refreshed by using the appointed refreshing file so as to refresh the firmware of the appointed array card to a version corresponding to the appointed refreshing file.

According to still another embodiment of the present application, there is provided a firmware refreshing apparatus of an array card, including: the device comprises an acquisition unit, a firmware refreshing unit and a control unit, wherein the acquisition unit is used for acquiring a firmware refreshing instruction, and the firmware refreshing instruction is used for indicating to carry out firmware refreshing on a designated array card on designated equipment; the execution unit is used for responding to the acquired firmware refreshing instruction and executing communication stopping operation, wherein the communication stopping operation is used for stopping interaction between the appointed array card and a group of target modules on the appointed equipment so as to enable a group of configuration files corresponding to the appointed array card to be in a refreshing permission state; and the refreshing unit is used for refreshing the firmware of the appointed array card by using the appointed refreshing file after the communication stopping operation is executed, so as to refresh the firmware of the appointed array card to a version corresponding to the appointed refreshing file.

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 embodiment provided by the application, a firmware refreshing instruction for indicating the designated array card on the designated equipment to refresh the firmware is obtained, and a communication stopping operation is executed in response to the obtained firmware refreshing instruction; therefore, after the firmware refreshing instruction is acquired, the interaction between the appointed array card and the target module can be stopped, so that the appointed array card can be in a state of not being read and written (not called), and the configuration file corresponding to the appointed array card is in a refreshing permission state; after the communication stopping operation is finished, the firmware of the appointed array card is refreshed by using the appointed refresh file, so that the firmware of the appointed array card can be completely refreshed to a version corresponding to the appointed refresh file in a state (refresh permission state) which is not called by the target module; the technical problem that the firmware refreshing method of the array card in the related technology has abnormal firmware refreshing of the array card is further solved; the technical effect of improving the refreshing efficiency of the array card firmware is achieved while the array card firmware is completely refreshed.

Drawings

FIG. 1 is a schematic diagram of an alternative firmware refreshing system for an array card according to an embodiment of the present application;

FIG. 2 is a schematic structural diagram of an alternative electronic device according to an embodiment of the present application;

FIG. 3 is a flow chart of an alternative firmware refreshing method of an array card according to an embodiment of the application;

FIG. 4 is a schematic diagram illustrating interaction between an alternative array card and a target module according to an embodiment of the present application;

FIG. 5 is a schematic diagram of an alternative array card interaction with an operating system provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of an alternative array card firmware refresh check provided by an embodiment of the present application;

FIG. 7 is a block diagram of an alternative firmware refresh apparatus for an array card in accordance with an embodiment of the present application;

fig. 8 is a block diagram of the architecture of a computer system of an alternative electronic device in accordance with an embodiment of the present application.

Detailed Description

In order that those skilled in the art will better understand the present application, a technical solution in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present application without making any inventive effort, shall fall within the scope of the present application.

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. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

The embodiment of the application provides a firmware refreshing method and device for an array card, a computer storage medium, an electronic device and a computer program product, which can improve the firmware refreshing efficiency of the array card, and the following describes an exemplary application of the electronic device provided by the embodiment of the application. An exemplary application when the device is implemented as a server will be described below.

Referring to fig. 1, fig. 1 is a schematic diagram of an alternative firmware refreshing system for an array card according to an embodiment of the present application;

according to one aspect of the embodiment of the application, a firmware refreshing method of an array card is provided. Alternatively, in the present embodiment, the firmware refreshing method of the array card described above may be applied to the firmware refreshing system of the array card shown in fig. 1. As shown in fig. 1, the firmware refresh system 100 of the array card may include: a server 101, a network 102 and a processing device 103. Wherein, to implement a firmware refresh application supporting an array card, server 101 may be coupled to processing device 103 via network 102, network 102 may include, but is not limited to, at least one of: wired network, wireless network. The wired network may include, but is not limited to, at least one of: a wide area network, a metropolitan area network, a local area network, and the wireless network may include, but is not limited to, at least one of: WIFI (Wireless Fidelity ), bluetooth.

The processing device 103 sends a firmware refreshing instruction to the server 101 through the network 102, wherein the firmware refreshing instruction is used for indicating to carry out firmware refreshing on a specified array card on the server 101; the server 101 receives a firmware refresh instruction transmitted by the processing device 103 through the network 102; the server 101 responds to the acquired firmware refreshing instruction and executes a communication stopping operation, wherein the communication stopping operation is used for stopping interaction between the appointed array card and a target module in the server 101 so as to enable a configuration file corresponding to the appointed array card to be in a refreshing permission state; after the communication stop operation execution is completed, the server 101 refreshes the firmware of the specified array card using the specified refresh file to refresh the firmware of the specified array card to a version corresponding to the specified refresh file, and obtains a firmware refresh result. The server 101 transmits the firmware refresh result to the processing device 103 through the network 102.

Here, the processing device 103 may send firmware refresh instructions to multiple servers at the same time, so as to improve the firmware refresh efficiency of the array card while completely refreshing the array card firmware of the multiple servers.

It should be noted that the above process can also be independently completed by the server 101, that is, the server 101 can automatically read the firmware refresh command to run the specified refresh file to refresh the firmware of the array card to a version corresponding to the specified refresh file in the automatic test flow through the firmware refresh command and the specified refresh file which are pre-deployed in the local storage unit in the absence of a network or other device connection.

The server 101 and the processing device 103 may be independent physical devices (for example, physical servers), or may be a device cluster (for example, a server cluster) or a distributed system formed by a plurality of physical devices, or may be a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, and basic cloud computing services such as big data and artificial intelligence platforms.

Referring to fig. 2, fig. 2 is a schematic structural diagram of an alternative electronic device according to an embodiment of the present application;

alternatively, in the present embodiment, the firmware refreshing method of the array card described above may be performed by an electronic device as shown in fig. 2. As shown in fig. 2, the electronic device 200 may be the server 101 or the processing device 103 described above, and the electronic device 200 includes: at least one process 201, at least one network interface 202, a bus system 203, and memory 204. The various components in the electronic device 200 are coupled together by a bus system 203. It is understood that the bus system 203 is used to enable connected communications between these components. The bus system 203 includes a power bus, a control bus, and a status signal bus in addition to the data bus. But for clarity of illustration the various buses are labeled as bus system 203 in fig. 2.

The processor 201 may be an integrated circuit chip with signal processing capabilities such as a general purpose processor, which may be a microprocessor or any conventional processor, or the like, a digital signal processor (DSP, digital Signal Processor), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or the like.

The memory 204 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid state memory, hard drives, optical drives, and the like. Memory 204 optionally includes one or more storage devices physically remote from processor 201.

Memory 204 includes volatile memory or nonvolatile memory, and may also include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read Only Memory (ROM), and the volatile Memory may be a random access Memory (RAM, random Access Memory). The memory 204 described in embodiments of the present application is intended to comprise any suitable type of memory.

In some embodiments, memory 204 is capable of storing data to support various operations, examples of which include programs, modules and data structures, or subsets or supersets thereof, as exemplified below.

An operating system 2041 including system programs for handling various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and handling hardware-based tasks;

network communication module 2042 for reaching other computing devices via one or more (wired or wireless) network interfaces 202, exemplary network interfaces 202 include: bluetooth, wireless compatibility authentication (WiFi), and universal serial bus (USB, universal Serial Bus), etc.;

In some embodiments, the device provided in the embodiments of the present application may be implemented in software, and fig. 2 shows a firmware refreshing device 2043 of an array card stored in a memory 204, which may be software in the form of a program and a plug-in, and includes the following software units: the acquisition unit, the execution unit, the refresh unit, these units are logical, so that any combination or further splitting can be made according to the implemented functions. The functions of the respective units will be described hereinafter.

In some embodiments, the server or the terminal device may implement the firmware refreshing method of the array card provided by the embodiment of the present application by running a computer program. For example, the computer program may be a native program or a software module in an operating system; a Native Application (APP) may be used, i.e. a program that needs to be installed in an operating system to be run; or an applet, i.e., a program that can be run only by being downloaded to a computer environment; but also an applet that can be embedded in any APP. In general, the computer programs described above may be any form of application, module or plug-in.

Along with the continuous development of the server industry, server models produced by server manufacturers are more and more diversified, service scenes of the servers are more and more abundant, and how to guarantee the reliability and availability of the shipment equipment becomes a problem that a server production end must consider.

The server (especially, the storage scenario) usually needs to be matched with the array card to perform hard disk management, and before the server leaves the factory, an automatic test is performed in a target operating system (for example, linux operating system) through a server diagnostic system (Diagnostic System, abbreviated as DIAG), and during the automatic test, the firmware version of the server array card is refreshed, so that the firmware versions of the array cards of the servers in the same batch are the same.

Because the automated testing through the server diagnostic system needs to be performed in the target operating system, part of the array card (for example, SAS3008 array card) cannot thoroughly refresh the firmware version in the target operating system, so that part of the configuration file remains, and thus the problems that the I2C channel is abnormal and cannot normally transmit data, and the like are caused, and the server production, testing and delivery efficiency are affected.

In the related art, the firmware refreshing is usually completed in a disk operating system (Disk Operating System, DOS for short), but the operating environment of the server diagnostic system (for example, linux operating system) cannot support the disk operating system, that is, the firmware refreshing is completed in the disk operating system, and cannot be implemented in an automated test process.

The reason for the problem is that when the array card of the hardware device performs firmware refreshing under the Linux operating system, information reading and information writing actions are always performed with other modules, related modules of the array card are continuously occupied, refreshing files cannot be completely written into the array card, and the disk operating system and the array card are completely free from interaction, so that refreshing can be normally completed.

According to the embodiment provided by the application, in the automatic test process, communication stopping operation is executed in response to the firmware refreshing instruction, interaction between the appointed array card and the target module on the appointed equipment is stopped, and the firmware of the appointed array card is refreshed by using the appointed refreshing file; the method can improve the refreshing efficiency of the array card firmware while completely refreshing the array card firmware, and avoid the defect that the related technology cannot automatically refresh the appointed array card firmware.

Alternatively, the firmware refreshing method of the array card may be performed by the server 101 alone, may be performed by the server 101 and the processing device 103 together, or may be performed by a processing device other than the server 101 and the processing device 103. As an alternative embodiment, the firmware refreshing method of the array card in this embodiment is exemplified by the execution of the server 101.

Referring to fig. 3, fig. 3 is a flowchart of an alternative firmware refreshing method of an array card according to an embodiment of the present application; as shown in fig. 3, the flow of the firmware refreshing method of the array card may include the following steps.

In step S301, a firmware refresh instruction is acquired.

The firmware refreshing instruction is used for indicating to carry out firmware refreshing on the appointed array card on the appointed device.

In some embodiments, a firmware refresh instruction is obtained that indicates a firmware refresh of a specified array card on a specified device, where the firmware refresh instruction may specify a firmware refresh of at least one array card of at least one of a plurality of servers.

Firmware (Firmware) is a program written in a Read-Only Memory (ROM), and serves as the most basic work of a system, i.e., directly controls hardware.

The array card comprises an independent redundant disk array card (Redundant Array of Independent Disks, abbreviated as RAID) and a serial additional memory card (Serial Attached SCSI Card, abbreviated as SAS), wherein the RAID card manages the disk array in the RAID system through hardware level control, and the operations comprise data reading and writing, data redundancy, data recovery and the like. SAS cards are commonly used in servers and data storage systems, and are high-speed storage interfaces for connecting and transmitting data, which can provide high-speed and reliable data transmission and support simultaneous connection of multiple devices.

The firmware refreshing instruction may be edited by a user in a program editing environment, and is used to update the specified firmware to the specified firmware version, where the firmware refreshing instruction may restore the firmware version of the specified device to a preset backup version, or may upgrade the firmware version of the specified device to the specified version.

According to the embodiment provided by the application, the firmware refreshing instruction for refreshing the version of the array card of the appointed equipment can be obtained, the firmware can be restored to the backup version through the firmware refreshing instruction when the firmware of the array card is abnormal, or the firmware of the array card can be updated to the appointed version through the firmware refreshing instruction, so that the firmware refreshing efficiency is improved.

In step S302, a communication stop operation is performed in response to the acquired firmware refresh instruction.

The communication stopping operation is used for stopping interaction between the designated array card and a set of target modules on the designated device so that a set of configuration files corresponding to the designated array card are in a refreshing permission state.

In some embodiments, the designated device, in response to obtaining the firmware refresh instruction, ceases interaction between the designated array card and a set of target modules on the designated device to place a set of configuration files corresponding to the designated array card in a refresh enabled state.

For example, in the data storage scenario, the server responds to the firmware refresh command, and stops interaction between the designated array card indicated by the firmware refresh command and an Operating System (OS), a baseboard management controller (Baseboard Management Controller, BMC), and a basic input output System (Basic Input Output System, BIOS), so that the configuration file corresponding to the designated array card is in a refresh enabled state.

Here, the configuration file corresponding to the specified array card is set in a refresh-allowed state, that is, the configuration file corresponding to the specified array card is set in a state not occupied by other programs or modules, for example, the configuration file corresponding to the specified array card is set in a state not read and not written (that is, the configuration file is not in a process of being used or called).

In some embodiments, the configuration file corresponding to the array card includes a file of information required to successfully execute the firmware refresh instruction (program), which is structured in a specific manner, and the configuration file is typically stored in a plain text file or a database file, which can be configured by the user.

According to the embodiment provided by the application, the designated device responds to the firmware refreshing instruction, and the interaction between the designated array card indicated by the firmware refreshing instruction and a group of target modules is stopped, so that the designated array card can be in an unread-write (not called) state, and the configuration file corresponding to the designated array card is in a refreshing permission state.

In step S303, after the communication stop operation execution is completed, the firmware of the specified array card is refreshed using the specified refresh file to refresh the firmware of the specified array card to a version corresponding to the specified refresh file.

In some embodiments, after the execution of the communication stop operation is completed, the designated device refreshes the firmware of the designated array card by using a preset firmware refresh file, so as to refresh the firmware of the designated array card to a version corresponding to the designated refresh file.

The firmware refreshing file is preset for refreshing a set of configuration files of the firmware of the array card, wherein the refreshing of the firmware of the appointed array card can be that the firmware of the appointed array card is updated in a normal use state of the array card; in the abnormal state of the array card data, the firmware of the designated array card may be restored (even if the firmware version is traced back to the preset backup version).

In some embodiments, the firmware refreshing file may be downloaded through a network or written by a user in a program editing environment, for example, the firmware refreshing file may be a sas3 flash (a firmware refreshing common application).

By the embodiment of the application, after the execution of the communication stopping operation of the array card of the appointed equipment is completed, the firmware version of the array card can be refreshed to the appointed version according to the user demand, so that the flexibility of firmware refreshing is improved.

Through the steps of the embodiment of the application, a firmware refreshing instruction is obtained, wherein the firmware refreshing instruction is used for indicating to refresh firmware of a designated array card on designated equipment; responding to the acquired firmware refreshing instruction, executing communication stopping operation, wherein the communication stopping operation is used for stopping interaction between the appointed array card and a group of target modules on the appointed equipment so as to enable a group of configuration files corresponding to the appointed array card to be in a refreshing permission state; after the communication stopping operation is executed, refreshing the firmware of the specified array card by using the specified refreshing file so as to refresh the firmware of the specified array card to a version corresponding to the specified refreshing file; the technical problem that the firmware refreshing method of the array card in the related technology has abnormal firmware refreshing of the array card is solved; the technical effect of improving the refreshing efficiency of the array card firmware is achieved while the array card firmware is completely refreshed.

In one exemplary embodiment, in response to the acquired firmware refresh instruction, performing a communication stop operation includes:

s11, responding to the acquired firmware refreshing instruction, and stopping interaction between the appointed array card and an operating system of the appointed device.

And S12, stopping interaction between the specified array card and the baseboard management controller of the specified device.

S13, stopping interaction between the appointed array card and the basic input and output system of the appointed device.

In some embodiments, the pointing device, in response to the obtained firmware refresh instruction, stops interaction between the pointing array card indicated by the firmware refresh instruction and the operating system of the pointing device, the baseboard management controller of the pointing device, and the basic input output system of the pointing device.

In some embodiments, the interaction between the array card and the operating system of the designated device, the baseboard management controller of the designated device, and the basic input output system of the designated device may be a read operation of the operating system of the designated device, the baseboard management controller of the designated device, and the basic input output system of the designated device on the data in the array card.

Referring to fig. 4, fig. 4 is a schematic diagram illustrating interaction between an optional array card and a target module according to an embodiment of the present application; the system comprises an operating system, a baseboard management controller, a basic input and output system and an array card.

Here, the array card may be SAS model 3008.

In some embodiments, the operating system of the specified device reads the hard disk information of the specified device through the store li64 tool and passes the hard disk information to the baseboard management controller, which can display the hard disk information through the visual interface.

The garcili 64 tool is an array card management tool, and can convert operation instructions into script forms so as to facilitate the operation of an operating system; the visual interface of the baseboard management controller may be a baseboard management controller web page (BMC web), and the operating system reads the hard disk information of the specified device in units of a period, where the period duration is positively related to the number of hard disks, for example, the period for the operating system to read the 36-bit disk array is 600 seconds.

In some embodiments, the basic input output system of the designated device reads the array controller information through the storage li library, wherein the array controller information comprises the model number of the array card, the firmware version information of the array card, RAID information in the array card and the like, and after the basic input output system reads the array controller information, the array controller information is sent to the baseboard management controller, and the baseboard management controller can manage various controller information (including the array controller information).

The array controller is used for managing a disk array, and the disk array is a disk system consisting of a plurality of independent disks; the store library is used to store hard disk (magnetic disk) information read by the store 64 tool.

In some embodiments, the baseboard management controller directly acquires the array card data through the ipmitool command, and the management controller acquires the array card data circularly in units of a period, for example, the period duration may be 4 seconds.

Here, operations related to an intelligent platform management interface (Intelligent Platform Management Interface, IPMI for short) may be performed through an ipmitool command, for example, obtaining server sensor information, restarting a server, setting user authority, etc.; IPMI is an industry standard employed to manage peripheral devices used in Intel-based enterprise systems.

Where ipmitool is a command line tool for managing and configuring IPMI-based servers, IPMI is a hardware management interface that allows for remote monitoring, management and control of various aspects of the servers, such as power control, sensor detection, event logging, etc.

For example, the array card data may be temperature sensor data of the array card, and the baseboard management controller obtains the temperature sensor data of the array card through an ipmitool command, and performs heat dissipation regulation based on the temperature sensor data.

According to the embodiment of the application, the read operation between the appointed array card and the appointed communication module can be stopped in response to the firmware refreshing instruction, so that the configuration file of the array card is in a refreshing permission state, and the success rate of firmware refreshing is improved.

In one exemplary embodiment, ceasing interaction of the designated array card with the operating system of the designated device includes:

s21, unloading the drive of the designated array card in the operating system of the designated device so as to terminate the interaction between the operating system of the designated device and the designated array card.

Referring to fig. 5, fig. 5 is a schematic diagram illustrating interaction between an optional array card and an operating system according to an embodiment of the present application. Including operating system, drivers, firmware, array cards.

In some embodiments, the driver for the designated array card is installed in the operating system, and the firmware for the designated array card is burned into the charged erasable programmable read-only memory (Electrically Erasable Programmable read only memory, EEPROM for short) of the array card, and when the operating system needs to read information from the array card, the operating system needs to access the firmware of the array card through the driver and realize the interaction operation with the array card through the firmware.

For example, the interactive operation may be input data, output data, array card management (e.g., expander management), and the like.

The Firmware (Firmware) is a program written into the erasable read-only memory or the electrically erasable programmable read-only memory, and the operating system can realize the operation action of the specific machine according to the corresponding device driver through the Firmware. A Driver (Driver) is a program code preset in an operating system, including information of a hardware device. The driver is a configuration file written by a hardware manufacturer according to an operating system, and the hardware in the computer without the driver cannot work normally.

In some embodiments, in order to terminate the interaction between the operating system of the specified device and the specified array card, it is necessary to make the driver or firmware not run normally, and since the firmware is burned into the array card and then the firmware refreshing (firmware burning) operation is also required, it is not suitable to be implemented by interference firmware.

For example, in a command line operating tool of the operating system, a "modprobe-r mpt3sas" command is executed, unloading the "mpt sas" driver of the designated array card.

Where "modprobe-r" is used to remove modules that have been added to the operating system, here, to remove the driver "mpt3sas".

By the embodiment of the application, the interaction between the array card and the operating system can be stopped in a mode of unloading the designated array card drive under the condition of not influencing firmware refreshing.

In one exemplary embodiment, stopping interaction between a designated array card and a baseboard management controller of a designated device includes:

s31, the baseboard management controller is started in a cold mode.

S32, executing the service stop command.

Wherein the service stop command is used to stop a service on the baseboard management controller to stop interaction between the designated array card and the baseboard management controller.

In some embodiments, to stop the interaction of the array card with the baseboard management controller, it is necessary to cold restart the baseboard management controller and execute a set of service stop commands.

For example, the baseboard management controller may continuously monitor the temperature of the array card in the server sensor data, and in order to stop the interaction of the array card with the baseboard management controller, it is necessary to cold restart the baseboard management controller by a "ipmitool mc reset cold" command and execute a set of service stop commands to suspend the baseboard management controller service.

The service pause command comprises a 'modprobe-r ipmi_msghand' command, a 'modprobe-r ipmi_devintf' command, a 'modprobe-r ipmi_si' command, a 'modprobe-r ipmi_poweroff' command and a 'modprobe-r ipmi_watch' command.

The "modprobe-r ipmi_msghand" command, the "modprobe-r ipmi_devintf" command, and the "modprobe-r ipmi_si" command are used for compiling the configuration baseboard management controller file; "modprobe-r ipmi_poweroff" is used for remote power off; the "modprobe-r ipmi_watchdog" command is used to close a WatchDog Timer (WatchDog Timer), which is an electronic or software Timer used to detect and recover from a computer failure. During normal operation, the computer will periodically reset the watchdog timer to prevent its loss.

After the execution of the service suspension command is completed, the service of the baseboard management controller is completely stopped, and at this time, the baseboard management controller cannot continue to communicate with the array card.

By the embodiment of the application, the baseboard management controller can be cold restarted and a service pause command can be executed to stop interaction between the array card and the baseboard management controller, so that the baseboard management controller is prevented from occupying related configuration files of the array card firmware.

In one exemplary embodiment, stopping interaction between a designated array card and a basic input output system of a designated device includes:

s41, controlling the basic input and output system to stop calling the target storage library so as to stop interaction between the designated array card and the basic input and output system.

The target memory bank is called by the basic input and output system for communicating with the appointed array card.

In some embodiments, to cease interaction between the array card of the designated device and the bios of the designated device, the bios is controlled based on the designated device to cease invoking the target repository to cease communication of the array card with the bios.

In some embodiments, in the set-up interface of the basic input output system, a Disable option (Disable) or change value to None is selected among the set-up options of the target repository.

For example, the target database may be a starlib library (a database of an array card management tool), and the basic input/output system is controlled to stop calling the starlib library, that is, the interaction between the array card and the basic input/output system may be stopped.

According to the embodiment provided by the application, the basic input/output system is stopped from calling the target database related to the array card firmware, so that the interaction between the array card and the basic input/output system is stopped, and the occupation of the basic input/output system on the related configuration files of the array card firmware is avoided.

s51, responding to the acquired firmware refreshing instruction, and calling an automation script to execute a communication stopping operation.

The automatic script is used for automatically executing communication stopping operation through a preset group of operation instructions.

In some embodiments, the specified device invokes the automation script to perform a communication stop operation in response to the acquired firmware refresh instruction, wherein the communication stop operation includes stopping interaction of the specified array card with an operating system of the specified device; stopping interaction between the specified array card and the baseboard management controller of the specified device; the interaction between the designated array card and the basic input output system of the designated device is stopped.

In some embodiments, the automated script is capable of automatically executing the firmware refreshing method of the array card according to the embodiments of the present application through a preset set of operation instructions based on the firmware refreshing instruction and the designated refreshing file.

In some embodiments, the server diagnostic system performs an automated test procedure that includes performing a communication shutdown operation of the array card by invoking an automated script to refresh firmware of the specified array card using the specified refresh file after the communication shutdown operation is completed.

In some embodiments, to ensure thorough refreshing of the array card firmware, the related services such as interaction between the array card and the operating system, the baseboard management controller, and the basic input/output system are stopped, and the related services need to be restored to normal operation after firmware refreshing, where the node may be restarted directly to achieve restoration of normal operation of the related services, for example, a "reboot" command is input under the system (used for restarting the designated device), and after the designated device is restarted, all services restore to normal operation.

According to the embodiment provided by the application, the communication stopping operation of the array card and the target module can be executed by calling the automation script, and the automation script can be deployed in the automatic test process of the server diagnosis system, so that the automation of the communication stopping operation in the process of refreshing the firmware of the array card is realized.

In an exemplary embodiment, the above method further comprises:

s61, after the firmware of the appointed array card is refreshed by using the appointed refresh file, a set of firmware information corresponding to the firmware of the appointed array card is exported.

S62, performing the following verification operation based on a set of firmware information to verify the refreshing result of the firmware of the designated array card.

S63, reading the version number in the group of firmware information to obtain a first version number.

And S64, checking the version number based on the first version number and the expected second version number.

S65, reading the model in the set of firmware information to obtain the target model.

And S66, performing model verification based on the target model and the preset model of the appointed array card.

S67, capturing specified keywords in a group of firmware information to obtain a capturing result of the specified keywords.

And S68, refreshing the integrity check based on the grabbing result of the specified keywords, wherein the specified keywords are keywords used for representing the unavailable state.

In some embodiments, the firmware refreshing of the array card is checked, but the firmware version number of the simple array card is checked to determine whether the firmware refreshing is complete, so that the firmware refreshing integrity of the array card is determined by checking the firmware information in the embodiment of the application.

In some embodiments, after the firmware of the specified array card is refreshed using the specified refresh file, the specified device derives firmware information corresponding to the specified firmware in response to the firmware verification instruction, and performs a verification operation on the refresh result of the firmware of the array card.

For example, the verification operation includes performing version number verification on the first version number after firmware refreshing and the second version number indicated by the designated refreshing file; the model checking is carried out on the model of the array card refreshed by the firmware and the preset model of the original array card; and carrying out refreshing integrity check based on the appointed keyword in the firmware information after firmware refreshing.

In some embodiments, the integrity of the firmware refresh is checked by "flashmap" data (a visual window for displaying firmware information); the "flashmap" data may be exported by "scrtnycli".

Here, the "flashmap" data is used to represent detailed information of firmware, including a version number, a product serial number, etc.; the scrtnycli tool is a command line tool for controlling and managing configuration files for deriving specified information.

In some embodiments, the first Version number after Firmware refreshing is obtained by capturing the keyword "Firmware Version", and if the first Version number after Firmware refreshing is the same as the second Version number indicated by the designated refresh file, the Version number of the array card Firmware is checked without errors.

In some embodiments, the model of the array card after firmware refreshing is obtained by capturing the keyword "Product Id", and if the model of the array card after firmware refreshing is the same as the preset model of the original array card, the model verification of the array card firmware is correct.

In some embodiments, the specified keyword after firmware refreshing is obtained by capturing the keyword "Not Available", and if "Not Available" exists, this indicates that the firmware refreshing is incomplete. "Not Available" may be a keyword indicating an unavailable state.

Referring to fig. 6, fig. 6 is an alternative array card firmware refresh check schematic diagram according to an embodiment of the present application.

As shown in fig. 6, the abnormal firmware information 601 is firmware information (Flashmap) of an array card firmware refresh abnormality of a model SAS 3008; the normal firmware information 602 is normal firmware information refreshed by the normal array card firmware.

The firmware information includes "NVDATA Version" for representing a nonvolatile data module Version of the array card firmware as "14.1.0.0" and "Vendor Version" for representing a Vendor Version of the array card firmware as "7.0.0.0". The "Config2" in the "Complete Flash" of the abnormal firmware information 601 is "Not Available", and information such as NVDATA cannot be read normally; the data information of the normal firmware information 602 is displayed intact, and the specified keyword "Not Available" (both "Available") does Not exist.

By the embodiment of the application, after the firmware refreshing of the array card, the integrity of the firmware refreshing can be checked in a plurality of checking modes so as to detect whether the firmware refreshing of the array card is complete.

Aiming at the problem that the firmware refreshing of the array card is incomplete, the embodiment of the application provides that the communication between the array card and the target module is stopped under a target operating system (such as a Linux operating system) so as to completely realize the firmware refreshing of the array card, and in the mass production scene of the server, the mass refreshing of the firmware of the array card of the server is realized in the form of an automatic script in the process of calling a server diagnosis system under the target operating system for automatic test. The problem that the refreshing of the array card firmware in the related technology is incomplete is solved, the test efficiency of the server is improved, and the equipment error reporting caused by the incomplete refreshing of the array card firmware is avoided.

It should be noted that, for simplicity of description, the foregoing method embodiments are all described as a series of acts, but it should be understood by those skilled in the art that the present application is not limited by the order of acts described, as some steps may be performed in other orders or concurrently in accordance with the present application. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily required for the present application.

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 embodiments 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 (such as ROM/RAM, magnetic disk, optical disk) comprising several 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 of the embodiments of the present application.

According to still another aspect of the embodiment of the present application, a firmware refreshing device for an array card is provided, and the device is used for implementing the firmware refreshing method for an array card provided in the foregoing embodiment, which is not described in detail. As used below, the terms "module," "unit" 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. 7 is a block diagram of an alternative firmware refreshing apparatus for an array card according to an embodiment of the present application, as shown in fig. 7, including:

an obtaining unit 701, configured to obtain a firmware refreshing instruction, where the firmware refreshing instruction is used to instruct firmware refreshing to a specified array card on a specified device;

an execution unit 702, configured to respond to the obtained firmware refresh instruction, and execute a communication stopping operation, where the communication stopping operation is used to stop interaction between the specified array card and a set of target modules on the specified device, so that a set of configuration files corresponding to the specified array card is in a refresh enabled state;

and a refreshing unit 703, configured to refresh the firmware of the specified array card using a specified refresh file after the communication stop operation is performed, so as to refresh the firmware of the specified array card to a version corresponding to the specified refresh file.

It should be noted that, the acquiring unit 701 in this embodiment may be used to perform the above-described step S301, the executing unit 702 in this embodiment may be used to perform the above-described step S302, and the refreshing unit 703 in this embodiment may be used to perform the above-described step S303.

In one exemplary embodiment, an execution unit includes:

the first stopping module is used for stopping interaction between the appointed array card and an operating system of the appointed device in response to the acquired firmware refreshing instruction;

The second stopping module is used for stopping interaction between the appointed array card and the baseboard management controller of the appointed device;

and the third stopping module is used for stopping the interaction between the appointed array card and the basic input and output system of the appointed device.

In one exemplary embodiment, the first stopping module includes:

and the unloading submodule is used for unloading the drive of the designated array card in the operating system of the designated equipment so as to terminate the interaction between the operating system of the designated equipment and the designated array card.

In one exemplary embodiment, the second stopping module includes:

the cold start sub-module is used for cold starting the baseboard management controller;

and the execution submodule is used for executing a service stop command, wherein the service stop command is used for stopping the service on the baseboard management controller so as to stop the interaction between the appointed array card and the baseboard management controller.

In one exemplary embodiment, the third stopping module includes:

and the control sub-module is used for controlling the basic input/output system to stop calling the target storage library so as to stop interaction between the designated array card and the basic input/output system, wherein the target storage library is a storage library called by the communication between the basic input/output system and the designated array card.

In one exemplary embodiment, an execution unit includes:

and the calling sub-module is used for responding to the acquired firmware refreshing instruction and executing communication stopping operation by calling an automatic script, wherein the automatic script is used for automatically executing the communication stopping operation through a preset group of operation instructions.

In an exemplary embodiment, the above apparatus further includes:

the export unit is used for exporting a group of firmware information corresponding to the firmware of the appointed array card;

an operation unit configured to perform the following verification operation based on a set of firmware information, to verify a refresh result of firmware of the specified array card:

the first reading unit is used for reading the version number in one group of firmware information to obtain a first version number;

the first verification unit is used for verifying the version number based on the first version number and the expected second version number;

the second reading unit is used for reading the model in the set of firmware information to obtain a target model;

the second verification unit is used for performing model verification based on the target model and the preset model of the appointed array card;

the grabbing unit is used for grabbing specified keywords in a group of firmware information to obtain grabbing results of the specified keywords;

And the third verification unit is used for refreshing the integrity verification based on the grabbing result of the specified keywords, wherein the specified keywords are keywords used for representing the unavailable state.

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; alternatively, the above modules may be located in different processors in any combination.

According to a further aspect of embodiments of the present application, there is also provided 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.

According to one aspect of the present application, there is provided a computer program product comprising a computer program/instruction containing program code for executing the method shown in the flow chart. In such an embodiment, referring to fig. 8, the computer program can be downloaded and installed from a network through the communication section 809 and/or installed from the removable media 811. When executed by the central processor 801, the computer program performs various functions provided by embodiments of the present application. The foregoing embodiment numbers of the present application are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.

Referring to fig. 8, fig. 8 is a block diagram of a computer system of an alternative electronic device according to an embodiment of the application.

Fig. 8 schematically shows a block diagram of a computer system of an electronic device for implementing an embodiment of the application. As shown in fig. 8, the computer system 800 includes a central processing unit 801 (Central Processing Unit, CPU) which can execute various appropriate actions and processes according to a program stored in a Read-Only Memory 802 (ROM) or a program loaded from a storage section 808 into a random access Memory 803 (Random Access Memory, RAM). In the random access memory 803, various programs and data required for system operation are also stored. The central processing unit 801, the read only memory 802, and the random access memory 803 are connected to each other through a bus 804. An Input/Output interface 805 (i.e., an I/O interface) is also connected to the bus 804.

The following components are connected to the input/output interface 805: an input portion 806 including a keyboard, mouse, etc.; an output portion 807 including a Cathode Ray Tube (CRT), a liquid crystal display (Liquid Crystal Display, LCD), and the like, and a speaker, and the like; a storage section 808 including a hard disk or the like; and a communication section 809 including a network interface card such as a local area network card, modem, or the like. The communication section 809 performs communication processing via a network such as the internet. The drive 810 is also connected to the input/output interface 805 as needed. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as needed so that a computer program read out therefrom is mounted into the storage section 808 as needed.

In particular, the processes described in the various method flowcharts may be implemented as computer software programs according to embodiments of the application. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via the communication section 809, and/or installed from the removable media 811. The computer programs, when executed by the central processor 801, perform the various functions defined in the system of the present application.

It should be noted that, the computer system 800 of the electronic device shown in fig. 8 is only an example, and should not impose any limitation on the functions and the application scope of the embodiments of the present application.

According to a further aspect of embodiments of the present 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.

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

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 embodiments 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 memory device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than what is shown or described, or they may be separately fabricated into individual integrated circuit modules, or a plurality of modules or steps in them may be fabricated into a single integrated circuit module. Thus, embodiments of the application are 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 embodiments of the present application, but various modifications and variations can be made to the embodiments of the present application by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the principle of the embodiments of the present application should be included in the protection scope of the embodiments of the present application.

Claims

1. A firmware refreshing method for an array card, comprising:

acquiring a firmware refreshing instruction, wherein the firmware refreshing instruction is used for indicating to refresh firmware of a designated array card on designated equipment;

responding to the acquired firmware refreshing instruction, and executing a communication stopping operation, wherein the communication stopping operation is used for stopping interaction between the appointed array card and a group of target modules on the appointed equipment so as to enable a group of configuration files corresponding to the appointed array card to be in a refreshing permission state;

after the communication stopping operation is executed, the firmware of the appointed array card is refreshed by using the appointed refreshing file so as to refresh the firmware of the appointed array card to a version corresponding to the appointed refreshing file.

2. The method of claim 1, wherein the performing a communication stop operation in response to the obtained firmware refresh instruction comprises:

responding to the acquired firmware refreshing instruction, and stopping interaction between the appointed array card and an operating system of the appointed device;

stopping interaction between the designated array card and a baseboard management controller of the designated device;

And stopping interaction between the designated array card and the basic input/output system of the designated device.

3. The method of claim 2, wherein the ceasing interaction of the specified array card with the operating system of the specified device comprises:

and unloading the drive of the specified array card in the operating system of the specified device so as to terminate the interaction between the operating system of the specified device and the specified array card.

4. The method of claim 2, wherein the ceasing interaction between the designated array card and the baseboard management controller of the designated device comprises:

cold starting the baseboard management controller;

and executing a service stop command, wherein the service stop command is used for stopping the service on the baseboard management controller so as to stop interaction between the appointed array card and the baseboard management controller.

5. The method of claim 2, wherein the ceasing interaction between the designated array card and the basic input output system of the designated device comprises:

and controlling the basic input/output system to stop calling a target storage library so as to stop interaction between the appointed array card and the basic input/output system, wherein the target storage library is a storage library called by the basic input/output system for communicating with the appointed array card.

6. The method of claim 1, wherein the performing a communication stop operation in response to the obtained firmware refresh instruction comprises:

and responding to the acquired firmware refreshing instruction, and executing the communication stopping operation by calling an automation script, wherein the automation script is used for automatically executing the communication stopping operation through a preset group of operation instructions.

7. The method of any of claims 1-6, wherein after the refreshing of the firmware of the specified array card using a specified refresh file, the method further comprises:

deriving a set of firmware information corresponding to firmware of the specified array card;

the following verification operation is performed based on the set of firmware information to verify the refresh result of the firmware of the specified array card:

reading version numbers in the group of firmware information to obtain a first version number; verifying the version number based on the first version number and the expected second version number;

reading the model in the set of firmware information to obtain a target model; model verification is carried out based on the target model and the preset model of the appointed array card;

Capturing specified keywords in the set of firmware information to obtain a capturing result of the specified keywords; and refreshing the integrity check based on the grabbing result of the specified keyword, wherein the specified keyword is used for representing the unavailable state.

8. A firmware refreshing apparatus for an array card, comprising:

the device comprises an acquisition unit, a firmware refreshing unit and a control unit, wherein the acquisition unit is used for acquiring a firmware refreshing instruction, and the firmware refreshing instruction is used for indicating to carry out firmware refreshing on a designated array card on designated equipment;

the execution unit is used for responding to the acquired firmware refreshing instruction and executing communication stopping operation, wherein the communication stopping operation is used for stopping interaction between the appointed array card and a group of target modules on the appointed equipment so as to enable a group of configuration files corresponding to the appointed array card to be in a refreshing permission state;

and the refreshing unit is used for refreshing the firmware of the appointed array card by using the appointed refreshing file after the communication stopping operation is executed, so as to refresh the firmware of the appointed array card to a version corresponding to the appointed refreshing file.

9. A computer readable storage medium having stored therein a computer program, wherein the computer program when executed by a processor implements the steps of the method of any of claims 1 to 7.

10. 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 implements the steps of the method as claimed in any one of claims 1 to 7 when the computer program is executed by the processor.