CN116955084A - Method, device, equipment and medium for managing case data - Google Patents

Method, device, equipment and medium for managing case data Download PDF

Info

Publication number
CN116955084A
CN116955084A CN202310953178.7A CN202310953178A CN116955084A CN 116955084 A CN116955084 A CN 116955084A CN 202310953178 A CN202310953178 A CN 202310953178A CN 116955084 A CN116955084 A CN 116955084A
Authority
CN
China
Prior art keywords
data
interrupt
management controller
baseboard management
hardware
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310953178.7A
Other languages
Chinese (zh)
Inventor
董强强
宋以强
刘清林
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Suzhou Inspur Intelligent Technology Co Ltd
Original Assignee
Suzhou Inspur Intelligent Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Suzhou Inspur Intelligent Technology Co Ltd filed Critical Suzhou Inspur Intelligent Technology Co Ltd
Priority to CN202310953178.7A priority Critical patent/CN116955084A/en
Publication of CN116955084A publication Critical patent/CN116955084A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3024—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a central processing unit [CPU]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3058—Monitoring arrangements for monitoring environmental properties or parameters of the computing system or of the computing system component, e.g. monitoring of power, currents, temperature, humidity, position, vibrations
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14—Handling requests for interconnection or transfer
    • G06F13/20—Handling requests for interconnection or transfer for access to input/output bus
    • G06F13/24—Handling requests for interconnection or transfer for access to input/output bus using interrupt

Abstract

The application provides a method, a device, equipment and a medium for managing case data, wherein the method for managing case data comprises the following steps: responding to the power-on of the chassis, a central processing unit of the chassis receives a hardware monitoring table issued by a management center of the cluster and issues the hardware monitoring table to a substrate management controller of the chassis; monitoring the data of the routine test of the hardware in the hardware monitoring table through the baseboard management controller, judging whether the data is changed compared with the data of the routine test of the last time, and triggering the interruption of the central processing unit in response to the change; the CPU judges whether the interrupt is triggered by the baseboard management controller, and in response to confirmation that the interrupt is triggered by the baseboard management controller, clears the interrupt and inquires the firmware layer data of the baseboard management controller so as to report the firmware layer data to the management center. The proposal disclosed by the application saves the occupation of CPU and link resources.

Description

Method, device, equipment and medium for managing case data
Technical Field
The present application relates to the field of storage, and in particular, to a method, an apparatus, a device, and a medium for chassis data management.
Background
The management center of the storage cluster is responsible for monitoring hardware states of all the chassis in the cluster, and performing inspection, abnormal data repair and alarm. In a centralized storage cluster, a BMC (Baseboard Management Controller ) may monitor the hardware data of the chassis.
In the related technology of chassis data management, a CPU (Central Processing Unit ) of the chassis reads hardware data of a BMC firmware layer to perform periodic routine test, compares whether the current data and the last data have changes, and if so, notifies a chassis management module to read the current data to perform inspection. This way, for the unchanged data read by each routine test of the CPU, the CPU and hardware resources are wasted, and the CPU and link resources are occupied.
Disclosure of Invention
In view of this, the present application provides a method, apparatus, device and medium for chassis data management, which at least solves the problems that in the above related technology of chassis data management, a CPU reads hardware data of a BMC firmware layer to perform periodic routine test, compares whether the current data and the last data have changes, and wastes CPU and hardware resources and occupies CPU and link resources for the data which are read by the CPU in each routine test.
Based on the above objects, an aspect of an embodiment of the present application provides a method for chassis data management, including: responding to the power-on of a chassis, a central processing unit of the chassis receives a hardware monitoring table issued by a management center of a cluster and issues the hardware monitoring table to a substrate management controller of the chassis; monitoring the data of the routine test of the hardware in the hardware monitoring table through the baseboard management controller, judging whether the data is changed compared with the data of the routine test of the hardware last time, and triggering the interrupt of the central processing unit in response to the change; the CPU judges whether the interrupt is triggered by the baseboard management controller, and in response to confirming that the interrupt is triggered by the baseboard management controller, clears the interrupt and inquires firmware layer data of the baseboard management controller so as to report the firmware layer data to the management center.
In some embodiments, the step of querying firmware layer data of the baseboard management controller to report it to the management center includes: creating a first queue and a second queue at an application layer of the central processing unit, respectively storing a setting task and a query task, wherein the first queue and the second queue respectively correspond to a channel; storing a first query task for querying firmware layer data of the baseboard management controller in the second queue; and taking out the first query task from the second queue according to the instruction type received by the application layer, and putting the first query task on one or two channels for execution so as to report the firmware layer data to the management center.
In some embodiments, the step of fetching the first query task from the second queue according to the instruction type received by the application layer and placing the first query task on one or two channels for execution, so as to report the firmware layer data to the management center includes: and responding to the inquiry command received by the application layer, taking out the first inquiry task from the second queue, and putting the first inquiry task on a channel corresponding to the second queue for execution so as to report the firmware layer data to the management center.
In some embodiments, the step of fetching the first query task from the second queue according to the instruction type received by the application layer and placing the first query task on one or two channels for execution, so as to report the firmware layer data to the management center further includes: responding to the application layer to receive a query instruction and a setting instruction, taking out a setting task from the first queue based on the setting instruction and putting the setting task on a channel corresponding to the first queue for execution, and judging whether the second queue is empty or not in response to the completion of the execution; and responding to the fact that the second queue is not empty, taking out the tasks in the second queue and executing the tasks through channels respectively corresponding to the first queue and the second queue so as to report the firmware layer data to the management center.
In some embodiments, the step of monitoring, by the baseboard management controller, the data of the present routine test of the hardware in the hardware monitoring table and determining whether there is a change compared with the data of the last routine test, and triggering the interrupt of the central processing unit in response to the change includes: monitoring the data of the routine test of the hardware in the hardware monitoring table through the baseboard management controller, judging whether the data is changed compared with the data of the routine test of the hardware last time, and judging whether an interrupt link exists between the baseboard management controller and the central processing unit or not in response to the change; in response to an interrupt link being present between the baseboard management controller and the central processor, an interrupt of an interrupt controller of the central processor is triggered by the interrupt link between the baseboard management controller and the central processor to notify the central processor of the change.
In some embodiments, the step of monitoring, by the baseboard management controller, the data of the current routine test of the hardware in the hardware monitoring table and determining whether there is a change compared with the data of the last routine test, and in response to the change, triggering the interrupt of the central processing unit further includes: in response to the absence of an interrupt link between the baseboard management controller and the central processor, the baseboard management controller sends a signal to a programmable logic device connected thereto, and based on the signal, triggers an interrupt of an interrupt controller of the central processor through the interrupt link between the programmable logic device and the central processor to notify the central processor of the change.
In some embodiments, the step of the central processor determining whether the interrupt was triggered by the baseboard management controller, in response to confirming that the interrupt was triggered by the baseboard management controller, clearing the interrupt and querying firmware layer data of the baseboard management controller to report it to the management center comprises: responsive to the interrupt controller of the central processing unit being triggered, the central processing unit sending an interrogation signal to the baseboard management controller, confirming whether the interrupt is triggered by the baseboard management controller according to a return result of the interrogation signal; and responding to the response signal corresponding to the inquiry signal received by the central processing unit, confirming that the interrupt is triggered by the baseboard management controller, clearing the interrupt, and inquiring the firmware layer data of the baseboard management controller so as to report the firmware layer data to the management center.
In another aspect of the embodiment of the present application, there is also provided an apparatus for chassis data management, including: the first module is used for responding to the power-on of the chassis, and the central processing unit of the chassis receives a hardware monitoring table issued by the management center of the cluster and issues the hardware monitoring table to the substrate management controller of the chassis; the second module is used for monitoring the data of the routine test of the hardware in the hardware monitoring table through the baseboard management controller, judging whether the data is changed compared with the data of the routine test of the hardware last time, and triggering the interruption of the central processing unit in response to the change; and the third module is used for judging whether the interrupt is triggered by the baseboard management controller by the central processing unit, and clearing the interrupt and inquiring the firmware layer data of the baseboard management controller to report the firmware layer data to the management center in response to confirming that the interrupt is triggered by the baseboard management controller.
In another aspect of the embodiment of the present application, there is also provided an electronic device including at least one processor; and a memory storing computer instructions executable on the processor, the instructions when executed by the processor performing the steps of the method described above.
In another aspect of the embodiments of the present application, there is also provided a computer-readable storage medium storing a computer program which, when executed by a processor, implements the method steps as described above.
The application has at least the following beneficial effects: the application provides a method for managing chassis data, which monitors routine test data of hardware needed by a management center through a BMC, only notifies a CPU of changed data to the management center, only occupies CPU and link resources when the routine test data of the hardware needed by the management center is changed, avoids occupying the CPU and link resources when the routine test is carried out on the hardware each time, saves the occupation of the CPU and the link resources, and improves the real-time response capability of the whole chassis to the changed data.
Further, two queues are created at the application layer to respectively place the query task and the setting task, the redundancy advantage of the two channels of the hardware channels corresponding to the two queues is fully utilized, the query task is supported to be executed by both channels at the same time, and the processing efficiency of the application layer to the query task is improved.
Further, when the queue where the setting task is located is empty, that is, the channel corresponding to the execution setting task is idle, the channel can execute the query task, that is, under the condition that the channel meets the high priority of the execution setting task, the execution completion setting task can support the execution of the query task, so that the load balance of the execution setting task and the execution of the query task is realized, and the execution pressure of the channel executing the query task is reduced.
Furthermore, the interrupt of the CPU can be triggered through different interrupt links according to different CPU types, so that the CPU management center is informed of the change of the data of the hardware required by the CPU management center, the flexibility of the system is improved, meanwhile, if the hardware type required by the management center is changed, only the hardware detection table issued by the management center is required to be configured correspondingly, firmware upgrading is not required to be carried out on the BMC, and the expandability is good.
Drawings
In order to more clearly illustrate the embodiments of the application or the solutions of the prior art, the drawings which are necessary for the description of the embodiments or the prior art will be briefly described, it being evident that the drawings in the following description are only some embodiments of the application and that other embodiments can be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart illustrating a method for chassis data management according to an embodiment of the present application;
fig. 2 is a schematic diagram of a hardware monitoring table issued by a management center according to an embodiment of the present application;
fig. 3 is a schematic diagram of a subscription table in a BMC according to an embodiment of the present application;
fig. 4 is a schematic diagram illustrating a mechanism for a BMC to actively report to a CPU according to an embodiment of the present application;
FIG. 5 is a schematic diagram showing a BMC triggering a CPU interrupt through a hardware link according to an embodiment of the present application;
FIG. 6 is another schematic diagram illustrating a BMC triggering a CPU interrupt through a hardware link according to an embodiment of the present application;
FIG. 7 is a schematic diagram of a ring queue of an application layer according to an embodiment of the present application;
FIG. 8 is a flowchart of a thread executing under a proxy model provided by an embodiment of the present application;
FIG. 9 is a schematic diagram of an apparatus for chassis data management according to an embodiment of the present application;
fig. 10 is a schematic diagram of an electronic device according to an embodiment of the present application;
fig. 11 is a schematic diagram of a computer-readable storage medium according to an embodiment of the present application.
Detailed Description
Embodiments of the present application are described below. However, it is to be understood that the disclosed embodiments are merely examples and that other embodiments may take various alternative forms.
Furthermore, it should be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
One or more embodiments of the present application will be described below with reference to the accompanying drawings.
The management center of the storage cluster is responsible for monitoring hardware states of all the chassis in the cluster, and performing inspection, abnormal data repair and alarm. In the centralized storage cluster, the BMC can monitor hardware data of the chassis and buffer the hardware data to the firmware layer, the CPU buffers the data of the periodic routine test of the hardware to the application layer through an IPMI (Intelligent Platform Management Interface ) protocol, the application layer of the CPU compares whether the data of the routine test of the hardware of the chassis and the data of the routine test of the last time have changes or not, and if the data have changes, a broadcast (broadcast) signal is sent to the management center to trigger the management center to patrol the buffered data. Besides the inquiry task, for the setting task of the management center, such as lighting, setting a nixie tube, upgrading firmware, repairing a power supply/fan/battery module and the like, a corresponding instruction is required to be issued to the BMC through an IPMI protocol by a CPU, that is, the task executed by the chassis in the storage cluster generally comprises the inquiry task and the execution task, and the data flow of the inquiry task is from the hardware layer of the chassis, the firmware layer of the chassis BMC, the application layer of the chassis CPU to the management center of the storage cluster; the data flow of the setting task is from the management center of the storage cluster, the application layer of the chassis CPU, the firmware layer of the chassis BMC to the hardware layer of the chassis.
The application layer is at CPU, the firmware layer is at BMC, the two are communicated through IPMI protocol, there are two physical links on hardware, LPC (Low Pin Count) link and network link respectively, the two are redundant each other. When the network link and the LPC link are normal, the network channel is used as a main channel, the LPC link is used as a standby channel, and the LPC channel is switched to only when the network channel cannot be used. The main implementation mode of the query task is that the chassis management data is listed in a table according to hardware types, such as a fan, a power supply, a controller, voltage, current, temperature and the like, through an application layer of a chassis CPU, each type corresponds to a fixed routine test period, after all data routine tests are completed, the data of the routine test is compared with the cached data of the last routine test, and when the data of the routine test is changed, a management center is triggered to carry out inspection through a broadcast signal.
Because of the limitations of the IPMI protocol itself and the physical channels, only a query/response mode can be implemented between the application layer and the firmware layer, the application layer of the CPU can only be the host end, and the firmware layer of the BMC can only be the target end. The data of the periodic routine test of the required hardware type monitored by the firmware layer is read to the application layer through the IPMI protocol, the data of each periodic routine test is required to be read to the application layer, the application layer judges whether the data has change or not, and for the data which has not changed and is read by each routine test of the CPU, CPU and hardware resources are wasted. Meanwhile, only one physical channel is used in the whole query process, when the query task and the setting task coexist, corresponding logic is designed on software to interrupt/restore the query task, the setting task is processed preferentially, the function of the double physical channels is not fully utilized, the execution pressure of a single physical channel is increased, the efficiency is very low, the system response is very slow, and when the data volume is increased, the physical channel is easy to cause a bottleneck.
Based on the above objects, a first aspect of the embodiments of the present application proposes an embodiment of a method for chassis data management. Fig. 1 is a flowchart of a method for chassis data management according to an embodiment of the present application, where, as shown in fig. 1, a method for chassis data management includes:
s1, responding to power-on of a chassis, a central processing unit of the chassis receives a hardware monitoring table issued by a management center of a cluster and issues the hardware monitoring table to a substrate management controller of the chassis;
s2, monitoring the data of the routine test of the hardware in the hardware monitoring table through the baseboard management controller, judging whether the data is changed compared with the data of the routine test of the last time, and triggering the interruption of the central processing unit in response to the change;
and S3, the central processing unit judges whether the interrupt is triggered by the baseboard management controller, and in response to confirming that the interrupt is triggered by the baseboard management controller, the interrupt is cleared and firmware layer data of the baseboard management controller are queried so as to report the firmware layer data to the management center.
The BMC monitors routine test data of hardware needed by the management center, only notifies the CPU of the changed data to the management center, and only occupies CPU and link resources when the routine test data of the hardware needed by the management center is changed, so that the CPU and link resources are prevented from being occupied when each time of routine test is carried out on the hardware, the occupation of the CPU and link resources is saved, and the real-time response capability of the whole chassis to the changed data is improved.
According to several embodiments of the present application, the step of querying firmware layer data of a baseboard management controller to report it to a management center includes: creating a first queue and a second queue at an application layer of a central processing unit, respectively storing a setting task and a query task, wherein the first queue and the second queue respectively correspond to a channel; storing a first query task for querying firmware layer data of the baseboard management controller in a second queue; and taking out the first query task from the second queue according to the type of the instruction received by the application layer, and putting the first query task on one or two channels for execution so as to report the firmware layer data to the management center. Two queues are created at the application layer to respectively place the query task and the setting task, the redundancy advantage of the two channels of the hardware channels corresponding to the two queues is fully utilized, the query task is supported to be executed by both channels at the same time, and the processing efficiency of the application layer on the query task is improved.
According to several embodiments of the present application, the step of fetching the first query task from the second queue according to the instruction type received by the application layer and executing the first query task on one or two channels to report the firmware layer data to the management center includes: and responding to the query instruction received by the application layer, taking out the first query task from the second queue, and putting the first query task on a channel corresponding to the second queue for execution so as to report the firmware layer data to the management center.
According to several embodiments of the present application, the step of retrieving the first query task from the second queue according to the type of the instruction received by the application layer and executing the first query task on one or two channels to report the firmware layer data to the management center further includes: responding to the application layer to receive the query instruction and the setting instruction, taking out the setting task from the first queue based on the setting instruction, putting the setting task on a channel corresponding to the first queue for execution, and responding to the completion of the execution, judging whether the second queue is empty; and responding to the fact that the second queue is not empty, taking out the tasks in the second queue and executing the tasks through channels respectively corresponding to the first queue and the second queue so as to report the firmware layer data to the management center. When the channel corresponding to the execution setting task is idle, the channel can execute the query task, namely, under the condition that the channel meets the high priority of the execution setting task, the execution completion setting task can support the execution of the query task, so that the load balance of the execution setting task and the execution of the query task is realized, and the execution pressure of the channel for executing the query task is reduced.
According to several embodiments of the present application, the step of monitoring, by the baseboard management controller, data of the present routine test of the hardware in the hardware monitoring table and determining whether there is a change compared with data of the last routine test thereof, and triggering an interrupt of the central processing unit in response to the change includes: monitoring the data of the routine test of the hardware in the hardware monitoring table through the baseboard management controller, judging whether the data is changed compared with the data of the routine test of the hardware last time, and judging whether an interrupt link exists between the baseboard management controller and the central processing unit or not in response to the change; in response to the presence of an interrupt link between the baseboard management controller and the central processor, an interrupt of the interrupt controller of the central processor is triggered by the interrupt link between the baseboard management controller and the central processor to notify the central processor of the change.
According to several embodiments of the present application, the step of monitoring, by the baseboard management controller, the data of the present routine test of the hardware in the hardware monitoring table and determining whether there is a change compared with the data of the last routine test thereof, and triggering the interrupt of the central processing unit in response to the change, further comprises: in response to the absence of an interrupt link between the baseboard management controller and the central processor, the baseboard management controller sends a signal to a programmable logic device connected thereto, and an interrupt of the interrupt controller of the central processor is triggered by the interrupt link between the programmable logic device and the central processor based on the signal to notify the central processor of the change.
According to several embodiments of the present application, the step of the central processor determining whether the interrupt is triggered by the baseboard management controller, clearing the interrupt and querying firmware layer data of the baseboard management controller to report it to the management center in response to confirming that the interrupt is triggered by the baseboard management controller comprises: responsive to the interrupt controller of the central processor being triggered, the central processor sending an interrogation signal to the baseboard management controller, confirming whether the interrupt is triggered by the baseboard management controller based on a return result of the interrogation signal; and responding to the response signal corresponding to the inquiry signal received by the central processing unit, confirming that the interrupt is triggered by the baseboard management controller, clearing the interrupt and inquiring the firmware layer data of the baseboard management controller so as to report the firmware layer data to the management center. According to different CPU types, the interrupt of the CPU is triggered through different interrupt links to inform the CPU that the data of the hardware required by the management center changes, so that the flexibility of the system is improved, meanwhile, if the hardware type required by the management center changes, only a hardware detection table issued by the management center is required to be configured correspondingly, firmware upgrading is not required to be carried out on the BMC, and the expandability is good.
The following is another embodiment of a method for managing chassis data according to the present application, firstly, obtain management data of hardware of a chassis required by a management center of a storage cluster, that is, a hardware monitoring table, may be configured as an xml format table according to needs and sent to a CPU of the chassis, after the chassis is powered on, when application layer software of the chassis CPU initializes, analyzes the xml table and sends it to a BMC through an IPMI interface, fig. 2 shows a schematic diagram of the hardware monitoring table sent by the management center provided by the embodiment of the present application, as shown in fig. 2, and subscribes it to the BMC, in this embodiment, subscribes the table to the BMC through the IPMI interface, and fig. 3 shows a schematic diagram of a subscription table in the BMC provided by the embodiment of the present application, and monitors periodic routine test data of hardware in the table through the BMC to determine whether to notify the CPU.
Fig. 4 is a schematic diagram of an active reporting mechanism of a BMC for a CPU provided by an embodiment of the present application, where, as shown in fig. 4, after the configuration of a subscription table is completed in the BMC, the BMC monitors data of periodic routine tests of corresponding hardware in the subscription table, and when the subscribed data changes, actively notifies an application layer of the CPU. The application layer needs to register interrupt in the kernel of CPU, when interrupt is triggered, the registered interrupt function is called, then judge whether BMC triggers the interrupt source, if yes, clear interrupt, start inquiry task, after triggering interrupt, the application layer sends IPMI frame, confirm whether BMC triggers interrupt. When the CPU confirms that the interrupt is triggered by the BMC, the application layer replies a response frame, the BMC clears the interrupt source after the report of the BMC is received, and then the application layer starts to inquire the firmware layer data through the IPMI protocol. The specific notification mode is realized through different hardware links according to different types of the CPU, and FIG. 5 shows a schematic diagram of the BMC provided by the embodiment of the application for triggering the CPU interrupt through the hardware link, wherein the BMC can trigger the interrupt directly through the interrupt link between the BMC and the CPU under the interrupt controller of the CPU; fig. 6 is another schematic diagram showing that the BMC triggers the CPU interrupt through the hardware link, where there is no interrupt link between the BMC and the CPU, and the BMC may multiplex the interrupt from the CPLD (Complex Programmable Logic Device ) to the CPU, where the BMC actively notifies the CPLD through the I2C (Inter-Integrated Circuit, serial communication protocol) bus, and then the CPLD triggers the interrupt through the interrupt link between the CPLD and the CPU to actively notify the application layer of the CPU.
In some embodiments, two task queues are set up at the application layer of the CPU using a queue data structure, each queue creating an execution thread, the two task queues storing set tasks and query tasks, respectively, and the two threads executing corresponding set threads and query threads, respectively. Preferably, the two queues may be configured as ring queues, as shown in fig. 7, and fig. 7 shows a schematic diagram of a ring queue of an application layer provided by an embodiment of the present application, where when there is a query or a set requirement, the application layer serves as a producer, places a query/set task into a corresponding task queue, and an execution thread serves as a consumer, and when it is detected that the queue is not empty, takes out the task to be executed, and executes the task (IPMI instruction). The set thread has a proxy mode, and fig. 8 shows a flowchart of an executing thread under the proxy model provided by the embodiment of the application, where the set thread preferentially detects a set queue, and when the set queue is not empty, an instruction is taken out to start executing a set task, and after all the set tasks are executed and the execution queue is empty, the query queue is actively executed. When both queues are empty, both threads are in a wait state. When one physical channel fails, the execution thread needs to start the proxy mode, i.e. the priority processing sets the task queue, and then the query task queue is processed. If the CPU is a multi-core processor, the interrupt controller can be arranged on one core, and when the CPU receives the interrupt triggered by the BMC, only one core is needed to process the interrupt and read the data of the firmware layer, so that the phenomenon that a plurality of cores participate in the interrupt and read the firmware data simultaneously to cause the waste of CPU resources is avoided.
In a second aspect of the embodiment of the present application, an apparatus for chassis data management is provided, and fig. 9 shows a schematic diagram of an apparatus for chassis data management according to an embodiment of the present application, as shown in fig. 9, including: a first module 011, configured to, in response to powering on a chassis, receive, by a central processor of the chassis, a hardware monitoring table issued by a management center of a cluster and issue the hardware monitoring table to a baseboard management controller of the chassis; a second module 012, configured to monitor, by the baseboard management controller, data of the present routine test of the hardware in the hardware monitoring table and determine whether there is a change compared with data of the last routine test thereof, and trigger, in response to the change, an interrupt of the central processing unit; and a third module 013, configured to, when the central processor determines whether the interrupt is triggered by the baseboard management controller, clear the interrupt and query firmware layer data of the baseboard management controller to report the firmware layer data to the management center in response to determining that the interrupt is triggered by the baseboard management controller.
In a third aspect of the embodiment of the present application, an electronic device is provided, and fig. 10 is a schematic diagram of an electronic device provided in the embodiment of the present application. As shown in fig. 10, an electronic device provided by an embodiment of the present application includes the following modules: at least one processor 021; and a memory 022, the memory 022 storing computer instructions 023 executable on the processor 021, the computer instructions 023 implementing the steps of the method as described above when executed by the processor 021.
The application also provides a computer readable storage medium. Fig. 11 is a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present application. As shown in fig. 11, the computer-readable storage medium 031 stores a computer program 032 which, when executed by a processor, performs the steps of the method as described above. The method performed is as above.
Finally, it should be noted that, as will be understood by those skilled in the art, implementing all or part of the above-described methods in the embodiments may be implemented by a computer program to instruct related hardware, and the program of the method for setting system parameters may be stored in a computer readable storage medium, where the program may include the flow of the embodiments of the methods described above when executed. The storage medium of the program may be a magnetic disk, an optical disk, a read-only memory (ROM), a random-access memory (RAM), or the like. The computer program embodiments described above may achieve the same or similar effects as any of the method embodiments described above.
Furthermore, the method disclosed according to the embodiment of the present application may also be implemented as a computer program executed by a processor, which may be stored in a computer-readable storage medium. The above-described functions defined in the methods disclosed in the embodiments of the present application are performed when the computer program is executed by a processor.
Furthermore, the above-described method steps and system units may also be implemented using a controller and a computer-readable storage medium storing a computer program for causing the controller to implement the above-described steps or unit functions.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as software or hardware depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
In one or more exemplary designs, the functions may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer or general purpose or special purpose processor. Further, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, D0L, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, digital Versatile Disc (DVD), floppy disk, blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
The foregoing is an exemplary embodiment of the present disclosure, but it should be noted that various changes and modifications could be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the disclosed embodiments described herein need not be performed in any particular order. Furthermore, although elements of the disclosed embodiments may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
It should be understood that as used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items.
The foregoing embodiment of the present application has been disclosed with reference to the number of embodiments for the purpose of description only, and does not represent the advantages or disadvantages of the embodiments.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, and the program may be stored in a computer readable storage medium, where the storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
Those of ordinary skill in the art will appreciate that: the above discussion of any embodiment is merely exemplary and is not intended to imply that the scope of the disclosure of embodiments of the application, including the claims, is limited to such examples; combinations of features of the above embodiments or in different embodiments are also possible within the idea of an embodiment of the application, and many other variations of the different aspects of the embodiments of the application as described above exist, which are not provided in detail for the sake of brevity. Therefore, any omission, modification, equivalent replacement, improvement, etc. of the embodiments should be included in the protection scope of the embodiments of the present application.

Claims (10)

1. A method of chassis data management, comprising:
responding to the power-on of a chassis, a central processing unit of the chassis receives a hardware monitoring table issued by a management center of a cluster and issues the hardware monitoring table to a substrate management controller of the chassis;
monitoring the data of the routine test of the hardware in the hardware monitoring table through the baseboard management controller, judging whether the data is changed compared with the data of the routine test of the hardware last time, and triggering the interrupt of the central processing unit in response to the change;
the CPU judges whether the interrupt is triggered by the baseboard management controller, and in response to confirming that the interrupt is triggered by the baseboard management controller, clears the interrupt and inquires firmware layer data of the baseboard management controller so as to report the firmware layer data to the management center.
2. The method of claim 1, wherein querying the firmware layer data of the baseboard management controller to report it to the management center comprises:
creating a first queue and a second queue at an application layer of the central processing unit, respectively storing a setting task and a query task, wherein the first queue and the second queue respectively correspond to a channel;
storing a first query task for querying firmware layer data of the baseboard management controller in the second queue;
and taking out the first query task from the second queue according to the instruction type received by the application layer, and putting the first query task on one or two channels for execution so as to report the firmware layer data to the management center.
3. The method of claim 2, wherein the step of fetching the first query task from the second queue and placing it on one or both channels for execution according to the type of instruction received by the application layer to report the firmware layer data to the management center comprises:
and responding to the inquiry command received by the application layer, taking out the first inquiry task from the second queue, and putting the first inquiry task on a channel corresponding to the second queue for execution so as to report the firmware layer data to the management center.
4. The method of claim 2, wherein the step of fetching the first query task from the second queue and placing it on one or both channels for execution according to the type of instruction received by the application layer to report the firmware layer data to the management center further comprises:
responding to the application layer to receive a query instruction and a setting instruction, taking out a setting task from the first queue based on the setting instruction and putting the setting task on a channel corresponding to the first queue for execution, and judging whether the second queue is empty or not in response to the completion of the execution;
and responding to the fact that the second queue is not empty, taking out the tasks in the second queue and executing the tasks through channels respectively corresponding to the first queue and the second queue so as to report the firmware layer data to the management center.
5. The method of claim 1, wherein the step of monitoring, by the baseboard management controller, data of the present routine test of the hardware in the hardware monitoring table and determining whether there is a change compared with data of the last routine test thereof, and in response to the change, triggering an interrupt of the central processing unit includes:
monitoring the data of the routine test of the hardware in the hardware monitoring table through the baseboard management controller, judging whether the data is changed compared with the data of the routine test of the hardware last time, and judging whether an interrupt link exists between the baseboard management controller and the central processing unit or not in response to the change;
in response to an interrupt link being present between the baseboard management controller and the central processor, an interrupt of an interrupt controller of the central processor is triggered by the interrupt link between the baseboard management controller and the central processor to notify the central processor of the change.
6. The method of claim 5, wherein the step of monitoring, by the baseboard management controller, the data of the present routine test of the hardware in the hardware monitoring table and determining whether there is a change compared with the data of the last routine test thereof, and in response to the change, triggering the interrupt of the central processing unit further comprises:
in response to the absence of an interrupt link between the baseboard management controller and the central processor, the baseboard management controller sends a signal to a programmable logic device connected thereto, and based on the signal, triggers an interrupt of an interrupt controller of the central processor through the interrupt link between the programmable logic device and the central processor to notify the central processor of the change.
7. The method of claim 1, wherein the step of the central processor determining whether the interrupt was triggered by the baseboard management controller, and in response to confirming that the interrupt was triggered by the baseboard management controller, clearing the interrupt and querying firmware layer data of the baseboard management controller to report it to the management center comprises:
responsive to the interrupt controller of the central processing unit being triggered, the central processing unit sending an interrogation signal to the baseboard management controller, confirming whether the interrupt is triggered by the baseboard management controller according to a return result of the interrogation signal;
and responding to the response signal corresponding to the inquiry signal received by the central processing unit, confirming that the interrupt is triggered by the baseboard management controller, clearing the interrupt, and inquiring the firmware layer data of the baseboard management controller so as to report the firmware layer data to the management center.
8. An apparatus for managing chassis data, comprising:
the first module is used for responding to the power-on of the chassis, and the central processing unit of the chassis receives a hardware monitoring table issued by the management center of the cluster and issues the hardware monitoring table to the substrate management controller of the chassis;
the second module is used for monitoring the data of the routine test of the hardware in the hardware monitoring table through the baseboard management controller, judging whether the data is changed compared with the data of the routine test of the hardware last time, and triggering the interruption of the central processing unit in response to the change;
and the third module is used for judging whether the interrupt is triggered by the baseboard management controller by the central processing unit, and clearing the interrupt and inquiring the firmware layer data of the baseboard management controller to report the firmware layer data to the management center in response to confirming that the interrupt is triggered by the baseboard management controller.
9. An electronic device, comprising:
at least one processor; and
a memory storing computer instructions executable on the processor, which when executed by the processor, perform the steps of the method of any one of claims 1-7.
10. A computer readable storage medium storing a computer program which when executed by a processor performs the steps of the method of any one of claims 1-7.
CN202310953178.7A 2023-07-31 2023-07-31 Method, device, equipment and medium for managing case data Pending CN116955084A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310953178.7A CN116955084A (en) 2023-07-31 2023-07-31 Method, device, equipment and medium for managing case data

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310953178.7A CN116955084A (en) 2023-07-31 2023-07-31 Method, device, equipment and medium for managing case data

Publications (1)

Publication Number Publication Date
CN116955084A true CN116955084A (en) 2023-10-27

Family

ID=88451064

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310953178.7A Pending CN116955084A (en) 2023-07-31 2023-07-31 Method, device, equipment and medium for managing case data

Country Status (1)

Country Link
CN (1) CN116955084A (en)

Similar Documents

Publication Publication Date Title
CN102692985B (en) The steady band external power control method of telemanagement formula computer system and system
US20100332884A1 (en) Storage control apparatus and method
US20120278552A1 (en) Remote execution of raid in large topologies
CN112764956A (en) Database exception handling system, and database exception handling method and device
JPH117315A (en) Monitor and control system and medium for recording the same processed content
JP5282569B2 (en) Management device, management system, management method, and management program
CN109032320B (en) Battery backup unit testing method and related equipment
EP2110748A2 (en) Cluster control apparatus, control system, control method, and control program
CN111309132B (en) Method for multi-gear power supply redundancy of server
CN116955084A (en) Method, device, equipment and medium for managing case data
CN114528163A (en) Automatic positioning system, method and device for server fault hard disk
CN111464357A (en) Resource allocation method and device
CN100490343C (en) A method and device for realizing switching between main and backup units in communication equipment
US20060026278A1 (en) Administration system for network management systems
JPH11120036A (en) Fault message output control system
CN112260902A (en) Network equipment monitoring method, device, equipment and storage medium
US9229886B2 (en) Management data transfer between processors
CN111159088A (en) IIC bus communication method and system based on heterogeneous multi-core processor
JP2953358B2 (en) Network monitoring equipment
CN117041172B (en) White box switch interface request processing method and device
CN116800604B (en) Configurable laser communication equipment control method, device, equipment and medium
JP3794358B2 (en) Power control method
KR20010048178A (en) The method for Server Process Remote Monitoring of the Telecommunication Network Management System
JPH08329023A (en) Parallel electronic computer system
CN115473809A (en) Configuration processing method and device based on micro-service architecture and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination