Reading control method, device, apparatus, and storage medium

Abstract

Embodiments of the present application provide a reading control method, device and equipment and a storage medium, the method comprising: receiving a target log entry sent by a baseboard management controller, the target log entry being generated by the baseboard management controller when detecting that data of a non-volatile node of an external device has changed; updating a state database according to the target log entry; and in response to the updating operation of the state database, reading data of the non-volatile node corresponding to the target log entry from the baseboard management controller, the embodiments of the present application detect that data of a non-volatile node of an external device has changed through a baseboard management controller, and update a target log entry carrying data change information of the non-volatile node to a state database of a CPU, so that the CPU only reads data when data of a non-volatile node of an external device has changed, thereby reducing unnecessary consumption of the CPU.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer application, in particular to a reading control method and device, equipment and storage medium. BACKGROUND

[0002] The baseboard management controller (BMC) is an independent system, which does not depend on other hardware (such as CPU, memory, etc.) on the system, and is usually used to monitor and manage the server, which includes the state monitoring and management of the server peripherals (such as fans, power supplies, etc.). With the wide application of white box switches in data centers, many switches also begin to use BMC to manage peripherals.

[0003] Although the BMC has an independent management address, the network management system does not directly manage the BMC when it is normally running, and still only takes the CPU plane as the management object. However, the CPU plane cannot directly read the data of these peripherals, so the BMC needs to provide an interface. In the read data, there are both easily variable data such as temperature value, fan speed, power voltage, and information that rarely changes such as device in place and field replace unit (FRU) information. Because the CPU cannot monitor the changes of these contents, an application is usually set to read immediately or read by a background task at a fixed time. Considering that the immediate reading needs to access the hardware to read in the BMC part, the reading speed is very slow, and a large number of peripherals are involved, and a lot of content needs to be read for each peripheral, so it often takes several minutes to read completely once, which cannot meet the requirements of some applications. Therefore, the background task reading method becomes the mainstream. In order to obtain information that is not too distorted, the reading period cannot be too long.

[0004] However, for these information that rarely changes, polling once every certain period is obviously very wasteful, and a lot of CPU is consumed unnecessarily. For the BMC whose performance is relatively weak, it is an additional burden. SUMMARY

[0005] The purpose of the embodiment of the present application is to provide a reading control method, device, equipment and storage medium, which solves the problem that the CPU is consumed unnecessarily and wasted due to frequent reading of non-variable data when reading BMC peripheral data, and increases the additional burden of the BMC whose performance is relatively weak. The specific technical solutions are as follows:

[0006] In the first aspect of the present application, a reading control method is first provided, characterized in that the method comprises:

[0007] receiving a target log item sent by a baseboard management controller, the target log item being generated by the baseboard management controller when detecting a change in data of a non-volatile node of an external device;

[0008] updating a state database according to the target log item;

[0009] reading data of the non-volatile node corresponding to the target log item from the baseboard management controller in response to an updating operation of the state database.

[0010] Optionally, the receiving a target log item sent by a baseboard management controller comprises:

[0011] sending an Rsyslog configuration file to the baseboard management controller;

[0012] receiving the target log item sent by the baseboard management controller through the Rsyslog configuration file.

[0013] Optionally, the updating a state database according to the target log item comprises:

[0014] sending the target log item to a first log file to generate target field information of the first log file;

[0015] triggering writing of the state database through the target field information.

[0016] Optionally, the triggering writing of the state database through the target field information comprises:

[0017] triggering writing of the state database when detecting that the target field information is consistent with preset characteristic information, the preset characteristic information being stored in an Rsyslog configuration file issued at a CPU end.

[0018] Optionally, the method further comprises:

[0019] starting a local daemon process in response to starting of a CPU;

[0020] reading data of an initial non-volatile node of the external device through the daemon process.

[0021] Optionally, after the reading data of the initial non-volatile node of the external device through the daemon process, the method further comprises:

[0022] subscribing to the state database;

[0023] reading data of a current non-volatile node of the external device from the baseboard management controller when subscribing to an updating event of the state database.

[0024] Optionally, the reading, from the baseboard management controller, of the data of the non-volatile node corresponding to the target log entry in response to the updating operation of the state database comprises:

[0025] In response to the updating operation of the state database, triggering a reading operation of a local daemon;

[0026] reading, by the reading operation, the data of the non-volatile node corresponding to the target log entry from the baseboard management controller.

[0027] In a second aspect of the embodiments of the present application, a reading control device is further provided, and has the characteristics that it comprises:

[0028] a first receiving module, configured to receive a target log entry sent by a baseboard management controller, the target log entry being generated by the baseboard management controller when detecting that the data of a non-volatile node of an external device has changed;

[0029] a first updating module, configured to update a state database according to the target log entry;

[0030] a first reading module, configured to read, from the baseboard management controller, the data of a non-volatile node corresponding to the target log entry in response to an updating operation of the state database.

[0031] In a third aspect of the embodiments of the present application, a communication device is further provided, and has the characteristics that it comprises a transceiver, a memory, a processor, and a program stored in the memory and executable on the processor;

[0032] The processor is configured to read the program in the memory to implement the reading control method.

[0033] In a fourth aspect of the embodiments of the present application, a computer readable storage medium is further provided, and has the characteristics that it stores instructions, and when the instructions are executed on a computer, the computer is caused to execute the reading control method.

[0034] The reading control method provided by the embodiment of the present application receives the target log item sent by the baseboard management controller, so that the baseboard management controller detects the data change of the non-volatile node of the external device, avoids the problem of large delay in reading by the CPU, updates the state database according to the target log item, so that the CPU determines that the data of the non-volatile node of the external device managed by the baseboard management controller has changed, reads the data of the non-volatile node corresponding to the target log item from the baseboard management controller in response to the update operation of the state database, so that the CPU only reads the data when it is determined that the data of the non-volatile node of the external device managed by the baseboard management controller has changed, and the unnecessary consumption of the CPU is reduced. The embodiment of the present application avoids the delay in reading by the CPU by detecting the data change of the non-volatile node of the external device by the baseboard management controller, and updates the target log item carrying the data change information of the non-volatile node to the state database of the CPU, so that the CPU only reads the data when the data of the non-volatile node of the external device managed by the baseboard management controller has changed, and the unnecessary consumption of the CPU is reduced. For the BMC which has weak performance, the burden is reduced. BRIEF DESCRIPTION OF DRAWINGS

[0035] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed to be used in the embodiments or the prior art description will be briefly introduced.

[0036] Figure 1 is a step flow chart of the reading control method provided by the embodiment of the present application;

[0037] Figure 2 is Figure 1 is a flow chart of step 101 of the reading control method provided by the embodiment of the present application;

[0038] Figure 3 is a second step flow chart of the reading control method provided by the embodiment of the present application;

[0039] Figure 4 is a third step flow chart of the reading control method provided by the embodiment of the present application;

[0040] Figure 5 is a structural schematic diagram of a reading control device provided by the embodiment of the present application;

[0041] Figure 6 is a structural schematic diagram of a communication device provided by the embodiment of the present application. DETAILED DESCRIPTION

[0042] In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be described in detail below with reference to the drawings. However, those skilled in the art can understand that, in the embodiments of the present application, many technical details are presented in order to make the readers better understand the present application. However, the technical solutions claimed by the present application can be implemented even without these technical details and based on various changes and modifications of the following embodiments. The division of the following embodiments is for the convenience of description, and should not constitute any limitation on the specific implementation of the present application, and the embodiments can be combined and referenced with each other without contradiction.

[0043] Referring to Figure 1 , one of the step flowcharts of the reading control method provided by the embodiments of the present application is shown, and the method can include:

[0044] In step 101, a target log item sent by a baseboard management controller is received, and the target log item is generated by the baseboard management controller when it is detected that the data of a non-volatile node of an external device has changed.

[0045] The baseboard management controller in the embodiments of the present application is a system independent of a CPU, and is a special controller for monitoring and managing a server / switch. The main functions include: device information management: recording server / switch information (model, manufacturer, date, production and technical information of each component, chassis information, mainboard information, etc.), BMC information (server / switch host name, IP, BMC firmware version, etc.); server state monitoring management: detecting and managing the health status such as temperature and voltage of each component (CPU, memory, hard disk, fan, frame, etc.) of the server / switch; remote control management of the server / switch: server power on / off, restart, maintenance, firmware update, system installation, etc.; maintenance management: log management, user management, BIOS management, alarm management, etc. Therefore, the CPU needs to manage the external device of the server / switch, and cannot directly access, and needs to provide a corresponding interface through the BMC to access, and the interface provided by the BMC can be a RESTful API or an IPMI interface, which is not specifically limited in the present application.

[0046] The data read by the CPU of the external device includes temperature values of volatile nodes, fan speeds, power supply voltages and other data of non-volatile nodes, and FRU information and other data of devices of non-volatile nodes which rarely change, because such reading is performed by accessing hardware in the BMC part, the reading speed is slow, and a large number of peripherals are involved, and a large amount of content needs to be read for each peripheral, so complete reading usually takes several minutes, therefore, the embodiment of the present application limits the reading of data of non-volatile nodes, and only when it is detected that the data of non-volatile nodes changes, the CPU is notified to read the data of non-volatile nodes, in addition, detecting the change of data of non-volatile nodes of the external device by the baseboard management controller can effectively avoid the problem of large delay caused by reading and judging by the CPU.

[0047] It should be noted that because the data of non-volatile nodes is information which rarely changes, when these data changes, the corresponding log level will change, and the log level is usually a warning level or a serious level, the embodiment of the present application distinguishes the changed non-volatile node data and the unchanged non-volatile node data based on the change of the log level, and takes the log entry of the level corresponding to the changed non-volatile node data as the target log entry which needs to be received by the CPU.

[0048] Step 102, updating the state database according to the target log entry.

[0049] In the embodiment of the present application, after the CPU receives the target log entry, the target log entry is sent to the first log file of the CPU, and then the target field information of the first log file is converted according to the preset rule, so that the first log file of the CPU changes, and then the field information in the first log file of the CPU is matched by the Rsyslog plug-in added at the CPU end, and when the Rsyslog plug-in matches the field information in the first log file of the CPU and the preset characteristic information exists, the state database is triggered to write, specifically, the state database is updated according to the target log entry, including:

[0050] The target log entry is sent to the first log file to generate target field information of the first log file;

[0051] The target field information triggers the state database to write. Wherein, the target field information triggers the state database to write, including:

[0052] In the case where it is detected that the target field information is consistent with the preset characteristic information, the state database is triggered to write, and the preset characteristic information is stored in the Rsyslog configuration file issued at the CPU end.

[0053] It should be noted that the preset rule is set by the module information and the level information of the log of the acquired non-volatile node, and the preset rule can set different field information according to different information carried by the target log entry, for example, the data change of the non-volatile node of different modules can be identified by the field information of the digital type, and the different level information of the target log entry can be identified by the field information of the letter type, and the preset feature information is set in the Rsyslog configuration file issued at the CPU end, and the preset feature information basically covers all the target field information converted by the preset rule from the log file of the data change of the non-volatile node.

[0054] In step 103, in response to the update operation of the state database, the data of the non-volatile node corresponding to the target log entry is read from the baseboard management controller.

[0055] In the embodiment of the application, the data of the non-volatile node of the baseboard management controller is read by the original daemon process of the CPU, wherein the daemon process is a special process running in the background, used to perform specific system tasks. Many daemon processes are started when the system is booted, and run until the system is turned off, and some are only started when needed, and automatically end after completing the task. The daemon process in the embodiment of the application is initially started with the system startup, and then does not periodically read the data of these non-volatile nodes, but waits until the data of the non-volatile node changes, and then triggers reading again. In order to achieve this purpose, the state database is set in the embodiment of the application, and the daemon process subscribes to the state database after reading the data of the non-volatile node in the initial startup, and only triggers reading the data of these non-volatile nodes after subscribing to the new update event of the state database.

[0056] Specifically, in response to the update operation of the state database, the data of the non-volatile node corresponding to the target log entry is read from the baseboard management controller, comprising:

[0057] In response to the update operation of the state database, the reading operation of the local daemon process is triggered;

[0058] The data of the non-volatile node corresponding to the target log entry is read from the baseboard management controller through the reading operation.

[0059] The reading control method provided by the embodiment of the application, by receiving the target log entry sent by the baseboard management controller, makes the baseboard management controller detect the data change of the non-volatile node of the external device, avoids the problem that the reading of the CPU is delayed for a long time, updates the state database according to the target log entry, so that the CPU determines that the data of the non-volatile node of the external device managed by the baseboard management controller has changed at this time, and reads the data of the non-volatile node corresponding to the target log entry from the baseboard management controller in response to the update operation of the state database, so that the CPU only reads the data when it is determined that the data of the non-volatile node of the external device managed by the baseboard management controller has changed, thereby reducing the unnecessary consumption of the CPU. The embodiment of the application avoids the delay of the reading of the CPU by detecting the data change of the non-volatile node of the external device by the baseboard management controller, and by updating the target log entry carrying the data change information of the non-volatile node to the state database of the CPU, so that the CPU only reads the data when the data of the non-volatile node of the external device managed by the baseboard management controller has changed, thereby reducing the unnecessary consumption of the CPU, and reducing the burden on the BMC which has weak performance.

[0060] With reference to Figure 2 , the reading control method provided by the embodiment of the application is shown Figure 1 The flow chart of step 101 of the reading control method provided by the embodiment of the application shown in FIG. 1 is specifically shown in FIG. 2, and specifically includes:

[0061] Step 201, sending an Rsyslog configuration file to the baseboard management controller.

[0062] The Rsyslog configuration file of the embodiment of the application is sent to the baseboard management controller by the CPU, so that the Rsyslog of the baseboard management controller can be synchronized to the CPU end when the log entry meeting the condition appears, wherein the Rsyslog configuration file can control the output of different types of logs by modifying parameters, can set the level of the logs according to different situations, and can also send the log entry meeting the condition to the target position by rules.

[0063] In addition, because the data of the non-volatile node changes, the log entry is generated locally by the Rsyslog service of the baseboard management controller, so the CPU end sends the Rsyslog configuration file to the baseboard management controller in order to monitor the data change of the non-volatile node of the external device of the baseboard management controller.

[0064] It should be noted that, because the external device of the baseboard management controller has both the data of the non-volatile node and the data of the volatile node, in order to avoid the data of the volatile node from interfering with the data of the non-volatile node, the data of the volatile node and the data of the non-volatile node are respectively stored in different Cache registers on the baseboard management controller.

[0065] In step 202, the target log item sent by the baseboard management controller is received through the Rsyslog configuration file.

[0066] In the embodiment of the application, the CPU sends the Rsyslog configuration file to the baseboard management controller, so that the Rsyslog on the baseboard management controller sends the log item to the Rsyslog on the CPU when a log item meeting the condition is generated, and the condition can be set by the level of the target log item, for example, when the level of the log is set as the warning level or the serious level, the log is sent to the Rsyslog on the CPU as the target log item.

[0067] The reading control method provided by the embodiment of the application receives the target log item sent by the baseboard management controller, so that the baseboard management controller detects the change of the data of the non-volatile node of the external device, avoids the problem of large delay in reading by the CPU, updates the state database according to the target log item, so that the CPU determines that the data of the non-volatile node of the external device managed by the baseboard management controller has changed, reads the data of the non-volatile node corresponding to the target log item from the baseboard management controller in response to the update operation of the state database, so that the CPU reads the data only when it is determined that the data of the non-volatile node of the external device managed by the baseboard management controller has changed, and the unnecessary consumption of the CPU is reduced. The embodiment of the application avoids the delay in reading by the CPU by detecting the change of the data of the non-volatile node of the external device by the baseboard management controller, and updates the target log item carrying the change information of the data of the non-volatile node to the state database of the CPU, so that the CPU reads the data only when the data of the non-volatile node of the external device managed by the baseboard management controller has changed, and the unnecessary consumption of the CPU is reduced. The burden on the BMC which has weak performance is reduced, and the specified log information can be synchronized to the CPU by the Rsyslog configuration of the baseboard management controller issued by the CPU.

[0068] Referring to Figure 3 , a second step flowchart of the reading control method provided by the embodiment of the application is shown, and specifically includes:

[0069] In step 301, in response to the start of the CPU, a local daemon process is started.

[0070] The daemon in the embodiment of the application is also started by default when the CPU is started for the first time.

[0071] In step 302, the daemon reads the data of the initial non-volatile node of the external device.

[0072] In the embodiment of the application, the daemon of the CPU reads the data of the initial non-volatile node of the external device after being started. In addition, because the external device includes volatile node data and non-volatile node data, the data of the volatile node needs to be frequently updated, so a fixed update period is set, and the volatile node data of the external device is read periodically according to the update period. The non-volatile node data does not change easily, so the daemon of the CPU only reads the data of the initial non-volatile node when it is started for the first time and then remains in a waiting state, and does not read the non-volatile node data of the external device periodically according to the update period.

[0073] In step 303, the state database is subscribed.

[0074] In the embodiment of the application, the daemon of the CPU reads the data of the initial non-volatile node of the external device in the baseboard management controller when it is started for the first time, and then remains in a background running waiting state without reading the non-volatile node data periodically. However, in order to trigger reading again when the data of the non-volatile node of the external device in the baseboard management controller changes, a state database is set at the CPU end, and the change of the data of the non-volatile node of the external device in the baseboard management controller is monitored through the state database. In order to confirm the monitoring result of the state database, the state database needs to be subscribed.

[0075] In step 304, in the case where it is subscribed that there is an update event in the state database, the data of the current non-volatile node of the external device is read from the baseboard management controller.

[0076] The subscription in the embodiment of the application is a method of obtaining the latest data of the state database at a low cost and in real time. Because the rsyslog plug-in of the CPU triggers writing the state database when it receives a specific log entry, the daemon in a background running waiting state triggers the operation of reading again after subscribing to the update event in the state database, and reads the data of the current non-volatile node of the external device from the baseboard management controller.

[0077] The reading control method provided by the embodiment of the present application receives the target log item sent by the baseboard management controller, so that the baseboard management controller detects the data change of the non-volatile node of the external device, avoids the problem of large delay in reading by the CPU, updates the state database according to the target log item, so that the CPU determines that the data of the non-volatile node of the external device managed by the baseboard management controller has changed at this time, reads the data of the non-volatile node corresponding to the target log item from the baseboard management controller in response to the update operation of the state database, so that the CPU only reads the data when it is determined that the data of the non-volatile node of the external device managed by the baseboard management controller has changed, thereby reducing the unnecessary consumption of the CPU. The embodiment of the present application avoids the delay in reading by the CPU by detecting the data change of the non-volatile node of the external device by the baseboard management controller, updates the target log item carrying the data change information of the non-volatile node to the state database of the CPU, so that the CPU only reads the data when the data of the non-volatile node of the external device managed by the baseboard management controller has changed, thereby reducing the unnecessary consumption of the CPU. For the BMC which has relatively weak performance, the burden is reduced, and the consumption of the CPU can be effectively reduced by subscribing to the state database through the daemon process to trigger the reacquisition of the data of the non-volatile node on the baseboard management controller.

[0078] Referring to Figure 4 , a third step flow chart of the reading control method provided by the embodiment of the present application is shown, which specifically includes:

[0079] The reading control method of the embodiment of the present application includes a baseboard management controller and a CPU. The baseboard management controller reads the data of the non-volatile node of the external device after starting. The CPU injects the Rsyslog configuration file to the baseboard management controller after starting. At this time, when the configuration file changes, the Rsyslog starts to synchronize the target log item meeting the condition to the CPU. The target field information of the CPU log file is generated according to the target log item. At this time, the Rsyslog of the CPU starts. After confirming that the meeting target field information is received, it is recorded in the state database. At this time, the subscribed state database has an update event, triggering the re-reading operation. At this time, the non-volatile node acquisition daemon reads the current data of the non-volatile node. The CPU starts the daemon for the first time, which also triggers the operation of immediately reading the data of the non-volatile node. After that, the daemon needs to subscribe to the state database to read the data of the non-volatile node. After the state database has an update event, triggering the re-reading operation, the non-volatile node acquisition daemon reads the current data of the non-volatile node again.

[0080] Referring to Figure 5 , a structure schematic diagram of a reading control device provided by the embodiment of the present application is shown, as shown in Figure 5 , the device can include:

[0081] The first receiving module 401 is configured to receive a target log item sent by a baseboard management controller, wherein the target log item is generated by the baseboard management controller when detecting that data of a non-volatile node of an external device changes;

[0082] The first updating module 402 is configured to update a state database according to the target log item;

[0083] The first reading module 403 is configured to read data of a non-volatile node corresponding to the target log item from the baseboard management controller in response to an updating operation of the state database.

[0084] Optionally, the first receiving module 401 further includes:

[0085] The first sending submodule is configured to send an Rsyslog configuration file to the baseboard management controller;

[0086] The first receiving submodule is configured to receive the target log item sent by the baseboard management controller through the Rsyslog configuration file.

[0087] Optionally, the first updating module 402 further includes:

[0088] The first generating submodule is configured to send the target log item to a first log file to generate target field information of the first log file;

[0089] The first triggering submodule is configured to trigger writing of the state database through the target field information.

[0090] Optionally, the first triggering submodule further includes:

[0091] The triggering unit is configured to trigger writing of the state database when detecting that the target field information is consistent with preset characteristic information, wherein the preset characteristic information is stored in an Rsyslog configuration file issued at a CPU end.

[0092] Optionally, the reading control apparatus further includes:

[0093] The second reading module is configured to start a local daemon process in response to starting of a CPU.

[0094] The third reading module is configured to read data of an initial non-volatile node of the external device through the daemon process.

[0095] The first subscribing module is configured to subscribe to the state database;

[0096] A fourth reading module is configured to read, in the case of subscribing to an update event existing in the state database, data of the non-volatile node of the current peripheral device from the baseboard management controller.

[0097] Optionally, the first reading module 403 further comprises:

[0098] A first obtaining sub-module is configured to trigger a reading operation of a local daemon in response to an update operation of the state database.

[0099] A first reading sub-module is configured to read, through the reading operation, data of the non-volatile node corresponding to the target log entry from the baseboard management controller.

[0100] The reading control method provided by the embodiment of the present application avoids the problem of large reading delay of the CPU by causing the baseboard management controller to detect the data change of the non-volatile node of the peripheral device, and updates the state database according to the target log entry, so that the CPU determines that the data of the non-volatile node of the peripheral device managed by the baseboard management controller has changed at this time, reads the data of the non-volatile node corresponding to the target log entry from the baseboard management controller in response to the update operation of the state database, and causes the CPU to read the data only when it is determined that the data of the non-volatile node of the peripheral device managed by the baseboard management controller has changed, thereby reducing the unnecessary consumption of the CPU. The embodiment of the present application avoids the delay of the CPU reading by detecting the data change of the non-volatile node of the peripheral device by the baseboard management controller, and updates the target log entry carrying the data change information of the non-volatile node to the state database of the CPU, so that the CPU reads the data only when the data of the non-volatile node of the peripheral device managed by the baseboard management controller has changed, thereby reducing the unnecessary consumption of the CPU and reducing the burden on the BMC which has relatively weak performance.

[0101] The embodiment of the present application also provides a communication device, as shown in the figure, comprising a processor 501, a communication interface 502, a memory 503 and a communication bus 504, wherein the processor 501, the communication interface 502 and the memory 503 complete mutual communication through the communication bus 504, Figure 6

[0102] The memory 503 is used to store a computer program.

[0103] The processor 501 is used to execute the program stored in the memory 503, and realizes the following steps:

[0104] The processor 501 is used to execute the program stored in the memory 503, and realizes the following steps:receive a target log entry sent by a baseboard management controller, wherein the target log entry is generated by the baseboard management controller when detecting that the data of a non-volatile node of a peripheral device has changed;

[0105] updating a state database according to the target log entry;

[0106] reading data of the non-volatile node corresponding to the target log entry from the baseboard management controller in response to the updating operation of the state database.

[0107] The communication bus mentioned above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For the convenience of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or only one type of bus.

[0108] The communication interface is used for communication between the terminal and other devices.

[0109] The memory can include a Random Access Memory (RAM) and can also include a non-volatile memory, such as at least one disk memory. Optionally, the memory can also be at least one storage device located away from the aforementioned processor.

[0110] The processor mentioned above can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc. It can also be a Digital Signal Processing (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

[0111] The application further provides a readable storage medium, when instructions in the storage medium are executed by a processor of an electronic device, the electronic device can execute the access control method of the foregoing embodiments.

[0112] For the device embodiment, it is basically similar to the method embodiment, so the description is relatively simple, and the related parts can be referred to the part of the method embodiment.

[0113] The algorithms and displays presented herein are not inherently related to any particular computer, virtual system, or other apparatus. Various systems can be constructed in accordance with the above description, and it is manifestly intended that the methods of the application can be practiced with the structures being apparent from the description. In addition, the present application is not intended to be limited to any particular programming language. It will be appreciated that a variety of programming languages can be used to implement the present application as described herein, and any references below to specific languages are provided for disclosure of enablement of the best mode of the application.

[0114] In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the application can be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been described in detail in order to not obscure the understanding of this description.

[0115] Similarly, it is to be understood that the mechanical details of the application sometimes are grouped into single embodiments, figures, or descriptions of related elements, for the purpose of brevity in the foregoing description. However, it is not to be construed that this method of disclosure was in any way intended to limit the claimed application to a single feature of the foregoing disclosure. Rather, it is the intent that each of the features from all individual embodiments should be addressed separately / individually. Accordingly, the claims appended hereto are hereby expressly incorporated into and made part of each of the following embodiments.

[0116] Those skilled in the art will appreciate that the modules in the apparatuses in the embodiments can be adapted and placed in one or more apparatuses other than the embodiments. The modules or units or components in the embodiments can be combined into one module or unit or component, and further can be divided into more sub-modules or sub-units or sub-components. Except that at least some of such features and / or processes or units are mutually exclusive, all combinations of all features disclosed in this specification (including the accompanying claims, abstract and drawings), and all processes or units of any methods or apparatuses disclosed so far can be adopted. Unless explicitly stated otherwise, each feature disclosed in this specification (including the accompanying claims, abstract and drawings) can be replaced by alternative features that provide the same, equivalent or similar functionality.

[0117] The various component embodiments of the present application can be implemented in hardware, or as software modules running in one or more processors, or in combinations thereof. As will be apparent to those of ordinary skill in the art, some or all of the functionality of some or all of the components in the sequencing apparatus according to the present application can be implemented using a microprocessor or a digital signal processor (DSP) in practice. The present application can also be implemented as a program for executing, in whole or in part, the methods described herein on a device or apparatus. Such a program embodying the present application can be stored on a computer-readable medium, or can be in the form of signals on one or more carriers. Such signals can be downloaded from an Internet website, or provided on a carrier, or in any other form.

[0118] It should be noted that the above-mentioned embodiments illustrate rather than limit the application, and that one skilled in the art will be able to design many alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word 'comprising' does not exclude the presence of elements or steps not listed in a claim. The word 'a' or 'an' preceding an element does not exclude the presence of a plurality of such elements. The application can be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the claims, the word 'first','second', 'third', etc. does not limit the number for these elements. These words are only used to distinguish between alternative claims. The mere fact that different claims depend on the same independent claim is not a reason for assuming that the dependent claims are mutually identical.

[0119] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the system, device and unit described above can refer to the corresponding processes in the foregoing method embodiments, which will not be described here.

[0120] The above only describes the preferred embodiments of the present application and is not intended to limit the present application. Any modification, equivalent replacement and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.

[0121] The above only describes the preferred embodiments of the present application and is not intended to limit the present application. Any modification, equivalent replacement and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.

[0122] It should be noted that the above-mentioned embodiments of the present application acquire various data related processes, which are carried out under the premise of complying with the corresponding data protection regulations and policies of the country where the location is located, and with the authorization given by the corresponding device owner.

Claims

1. A read control method, characterized in that, The method includes: The system receives a target log entry sent by the baseboard management controller. The target log entry is generated by the baseboard management controller when it detects a change in the data of a non-volatile node of an external device. When the data of the non-volatile node of the external device changes, the level of the corresponding log entry changes to either a warning level or a critical level. The system determines whether the data of the non-volatile node of the external device has changed based on the level change of the log entry. Update the status database based on the target log entries; In response to the update operation of the state database, data of the non-volatile node corresponding to the target log entry is read from the baseboard management controller.

2. The method according to claim 1, characterized in that, The target log entries sent by the receiving baseboard management controller include: Send the Rsyslog configuration file to the substrate management controller; The target log entries sent by the baseboard management controller are received through the Rsyslog configuration file.

3. The method according to claim 1, characterized in that, The step of updating the status database based on the target log entry includes: The target log entry is sent to the first log file to generate the target field information of the first log file; The target field information triggers the write status database.

4. The method according to claim 3, characterized in that, The step of triggering the write status database through the target field information includes: If the target field information is found to be consistent with the preset feature information, the write status database is triggered. The preset feature information is stored in the Rsyslog configuration file issued by the CPU.

5. The method according to claim 1, characterized in that, Also includes: In response to CPU startup, a local daemon process is started; The daemon process reads the data from the initial non-volatile node of the external device.

6. The method according to claim 5, characterized in that, After reading the data of the initial non-volatile node of the external device through the daemon process, the method further includes: Subscribe to the state database; If an update event is detected in the state database, the data of the non-volatile node of the current external device is read from the baseboard management controller.

7. The method according to claim 1, characterized in that, The step of responding to the update operation of the state database by reading data of the non-volatile node corresponding to the target log entry from the baseboard management controller includes: In response to the update operation of the state database, a read operation is triggered in the local daemon process; The read operation reads the data of the non-volatile node corresponding to the target log entry from the baseboard management controller.

8. A reading control device, characterized in that, include: The first receiving module is used to receive target log entries sent by the baseboard management controller. The target log entries are generated by the baseboard management controller when it detects a change in the data of a non-volatile node of an external device. When the data of the non-volatile node of the external device changes, the level of the corresponding log entry changes to a warning level or a critical level. The module determines whether the data of the non-volatile node of the external device has changed based on the level change of the log entry. The first update module is used to update the status database based on the target log entries; The first reading module is used to read data of the non-volatile node corresponding to the target log entry from the baseboard management controller in response to the update operation of the status database.

9. A communication device, characterized in that, include: A transceiver, a memory, a processor, and a program stored in the memory and executable on the processor; The processor is configured to read a program from the memory to implement the steps of the read control method as described in any one of claims 1-7.

10. A readable storage medium for storing a program, characterized in that, When the program is executed by the processor, it implements the steps of the read control method as described in any one of claims 1-7.

Images