CN107608868B - Log collection method, Baseboard Management Controller (BMC) and disk controller - Google Patents

Log collection method, Baseboard Management Controller (BMC) and disk controller Download PDF

Info

Publication number
CN107608868B
CN107608868B CN201710811006.0A CN201710811006A CN107608868B CN 107608868 B CN107608868 B CN 107608868B CN 201710811006 A CN201710811006 A CN 201710811006A CN 107608868 B CN107608868 B CN 107608868B
Authority
CN
China
Prior art keywords
bmc
log
log collection
disk controller
description information
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.)
Active
Application number
CN201710811006.0A
Other languages
Chinese (zh)
Other versions
CN107608868A (en
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.)
Lenovo Beijing Ltd
Original Assignee
Lenovo Beijing 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 Lenovo Beijing Ltd filed Critical Lenovo Beijing Ltd
Priority to CN201710811006.0A priority Critical patent/CN107608868B/en
Publication of CN107608868A publication Critical patent/CN107608868A/en
Application granted granted Critical
Publication of CN107608868B publication Critical patent/CN107608868B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Debugging And Monitoring (AREA)

Abstract

The present disclosure provides a log collection method, including: sending a log collection command to a disk controller through a Baseboard Management Controller (BMC) on a server mainboard, wherein the log collection command at least carries indication information for indicating the disk controller to scan a log file on a specified position; and after the disk controller scans the log file at the designated position according to the indication of the indication information and returns the scanning content, receiving the scanning content returned by the disk controller through the BMC. The disclosure also provides another log collection method, a baseboard management controller BMC and a disk controller.

Description

Log collection method, Baseboard Management Controller (BMC) and disk controller
Technical Field
The present disclosure relates to a log collection method, a Baseboard Management Controller (BMC) and a disk Controller.
Background
In case of performing problem analysis on a System, a System log is generally very important, but in the related art, an Operating System (OS) is generally required to be logged in when the System log is collected.
In the course of implementing the embodiments of the present disclosure, the inventors found that the foregoing related art has at least the following drawbacks: logging on to the operating system to collect the system log requires an OS password and affects the traffic.
Disclosure of Invention
One aspect of the present disclosure provides a log collection method, including sending a log collection command to a disk controller through a baseboard management controller BMC on a server motherboard, where the log collection command carries at least indication information for indicating the disk controller to scan a log file at a specified location; and after the disk controller scans the log file at the designated position according to the instruction of the instruction information and returns the scanning content, receiving the scanning content returned by the disk controller through the BMC.
According to the embodiment of the disclosure, sending a log collection command to a disk controller through a Baseboard Management Controller (BMC) on a server mainboard comprises detecting whether a log collection condition is met; and if the log collection condition is detected to be met, triggering the BMC to send the log collection command to the disk controller.
According to an embodiment of the present disclosure, detecting whether a log collection condition is satisfied includes detecting whether an externally input log collection request is received; and/or detecting whether a preset log collection time is reached.
According to an embodiment of the disclosure, the log collection method further includes predefining file description information in the BMC, where the file description information includes location description information describing a location where each log file is located.
According to an embodiment of the present disclosure, the method for collecting logs further includes before the BMC sends the log collection command to the disk controller, determining whether the designated location is one or more of locations described by the location description information included in the file description information; and if the specified position is judged not to be one or more of the positions described by the position description information contained in the file description information, prohibiting the BMC from sending the log collection command to the disk controller.
Another aspect of the present disclosure provides another log collection method, including receiving a log collection command sent by a baseboard management controller BMC on a server motherboard to a disk controller, where the log collection command at least carries indication information for indicating the disk controller to scan a log file at a specified location; scanning the log file at the designated position according to the indication of the indication information; and returning the corresponding scanning content to the BMC.
Another aspect of the present disclosure further provides a baseboard management controller BMC, disposed on a server motherboard, for performing log collection, where the baseboard management controller BMC includes a first sending module, configured to send a log collection command to a disk controller, where the log collection command at least carries indication information for indicating the disk controller to scan a log file at a specified location; and a second receiving module, configured to receive the scanned content returned by the disk controller after the disk controller scans the log file at the specified location according to the instruction of the instruction information and returns the scanned content.
According to an embodiment of the present disclosure, the BMC further includes a predefined module, configured to predefine file description information in the BMC, where the file description information includes location description information describing a location where each log file is located.
According to an embodiment of the present disclosure, the BMC further includes a determining module, configured to determine whether the designated location is one or more of the locations described by the location description information included in the file description information before the BMC sends the log collection command to the disk controller; and an authority limiting module, configured to prohibit the BMC from sending the log collection command to the disk controller if it is determined that the designated location is not one or more of the locations described by the location description information included in the file description information.
Another aspect of the present disclosure further provides a disk controller, configured to perform log collection, where the disk controller includes a second receiving module, configured to receive a log collection command sent by a baseboard management controller BMC on a server motherboard to the disk controller, where the log collection command at least carries indication information for indicating the disk controller to scan a log file in a specified location; the scanning module is used for scanning the log file on the specified position according to the indication of the indication information; and the second sending module is used for returning the corresponding scanning content to the BMC.
Drawings
For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:
fig. 1 schematically shows an application scenario suitable for a log collection method, a baseboard management controller BMC, and a disk controller according to an embodiment of the present disclosure;
FIG. 2 schematically illustrates a flow chart of a log collection method according to an embodiment of the present disclosure;
fig. 3A schematically shows a flowchart of sending a log collection command to a disk controller by a baseboard management controller BMC on a server motherboard according to an embodiment of the present disclosure;
FIG. 3B schematically shows a flow diagram for detecting whether log collection conditions are met, in accordance with an embodiment of the present disclosure;
FIG. 3C schematically shows a flow chart of a log collection method according to another embodiment of the present disclosure;
FIG. 4 schematically illustrates a flow chart of a log collection method according to another embodiment of the present disclosure;
FIG. 5 schematically illustrates a block diagram of a baseboard management controller BMC according to an embodiment of the disclosure;
FIG. 6A schematically illustrates a block diagram of a baseboard management controller BMC according to another embodiment of the disclosure;
FIG. 6B schematically illustrates a block diagram of a baseboard management controller BMC according to another embodiment of the disclosure;
FIG. 7 schematically illustrates a block diagram of a disk controller according to an embodiment of the present disclosure; and
FIG. 8 schematically illustrates a block diagram of a computer system that can implement a log collection method according to an embodiment of the disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The words "a", "an" and "the" and the like as used herein are also intended to include the meanings of "a plurality" and "the" unless the context clearly dictates otherwise. Furthermore, the terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.
Some block diagrams and/or flow diagrams are shown in the figures. It will be understood that some blocks of the block diagrams and/or flowchart illustrations, or combinations thereof, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the instructions, which execute via the processor, create means for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks.
Accordingly, the techniques of this disclosure may be implemented in hardware and/or software (including firmware, microcode, etc.). In addition, the techniques of this disclosure may take the form of a computer program product on a computer-readable medium having instructions stored thereon for use by or in connection with an instruction execution system. In the context of this disclosure, a computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the instructions. For example, the computer readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. Specific examples of the computer readable medium include: magnetic storage devices, such as magnetic tape or Hard Disk Drives (HDDs); optical storage devices, such as compact disks (CD-ROMs); a memory, such as a Random Access Memory (RAM) or a flash memory; and/or wired/wireless communication links.
The embodiment of the disclosure provides a log collection method, a Baseboard Management Controller (BMC) and a disk controller, wherein the log collection method comprises the steps of sending a log collection command to the disk controller through the BMC on a server mainboard, wherein the log collection command at least carries indication information for indicating the disk controller to scan a log file on a specified position; and after the disk controller scans the log file at the designated position according to the indication of the indication information and returns the scanning content, receiving the scanning content returned by the disk controller through the BMC.
Fig. 1 schematically shows an application scenario suitable for the log collection method, the baseboard management controller BMC, and the disk controller according to an embodiment of the present disclosure.
As shown in fig. 1, the application scenario 100 of this embodiment may include a server 101 (also referred to as a host) and a terminal device 102. Further, the server 101 includes a baseboard management controller BMC, a disk controller, and a memory (not shown). The terminal device 102 may be installed with various systems, such as but not limited to a Windows operating system and/or a Linux operating system. Generally, when a user uses the terminal device 102, these systems generate a large amount of log files, and the log files of the systems are usually very important in the process of problem analysis of the systems. Therefore, it is necessary to collect the log files, and at this time, the collection of the log files may be realized by using the server 101, specifically, by using the baseboard management controller BMC and the disk controller included in the server 101.
It should be noted that the application scenarios in the present embodiment are only illustrative and do not limit the scope of the present disclosure.
Fig. 2 schematically shows a flow chart of a log collection method according to an embodiment of the present disclosure.
As shown in fig. 2, the log collecting method may include operations S201 and S202, in which:
in operation S201, a log collection command is sent to the disk controller through the BMC on the server motherboard, where the log collection command at least carries indication information for indicating the disk controller to scan a log file at a specified location.
It should be noted that the baseboard management controller is mounted on the server motherboard. The log file, especially the log file of the operating system, may be stored in a designated location (e.g., a C-disk, etc.) of the server, and when the user needs to collect the log file, the baseboard management controller BMC may send a log collection command to the disk controller (for controlling the hard disk/floppy disk, allocating resources, and adjusting data input/output), so that the disk controller completes collection of the log file. However, in order to ensure that the disk controller can quickly find the log file in the server, the log collection command sent by the BMC to the disk controller may carry at least one indication information that may be used to instruct the disk controller to scan the log file at a specified location in the server (i.e., collect the log file at the specified location) at the same time.
It should be understood that the designated positions in the embodiments of the present disclosure may include one or more, and are not limited herein.
In operation S202, after the disk controller scans the log file at the designated location according to the instruction of the instruction information and returns the scanned content, the scanned content returned by the disk controller is received by the BMC.
In the embodiment of the present disclosure, the disk controller needs to return the scan content to the BMC, the BMC receives the returned scan content and stores the scan content in the corresponding memory, and when the user sends a request to read the log file, the BMC executes the operation and further sends the scan content stored in the memory to the user.
It should be noted that the memory in the embodiment of the present disclosure may be an external storage device for storing the log file alone, or may be one or more memories inside a server for storing the log file, which is not limited herein.
According to the embodiment of the disclosure, the baseboard management controller BMC sends the log collection command to the disk controller, and then the disk controller scans the log file and returns the scanning content to the baseboard management controller BMC, so that the purpose of collecting the log is achieved on the premise that an operating system does not need to be logged in, an operating system password does not need to be input, and the service of the operating system is not influenced.
The method shown in fig. 2 is further described with reference to fig. 3A-3C in conjunction with specific embodiments.
Fig. 3A schematically shows a flowchart of sending a log collection command to a disk controller by a baseboard management controller BMC on a server motherboard according to an embodiment of the present disclosure.
In this embodiment, the log collection method may include operations S301 and S302 (i.e., operation S201 may include operations S301 and S302) in addition to operation S202 described above with reference to fig. 2. The description of operation S202 is omitted here for the sake of brevity of description. As shown in fig. 3A, wherein:
in operation S301, it is detected whether a log collection condition is satisfied.
In operation S302, if it is detected that the log collection condition is satisfied, the BMC is triggered to send a log collection command to the disk controller.
In embodiments of the present disclosure, the log collection condition may include a variety of conditions, including, for example, but not limited to, an event condition and a time condition. Further, the event condition may include, but is not limited to, a log collection request sent by the user, and the time condition may include, but is not limited to, a preset log collection time.
Specifically, when the baseboard management controller BMC sends the log collection command to the disk controller, it may first detect whether the log collection condition is satisfied, for example, whether the event condition is satisfied, and/or whether the time condition is satisfied, and if it is detected that one or more of the conditions are satisfied, the baseboard management controller BMC may be triggered to send the log collection command to the disk controller.
Through the embodiment of the disclosure, the relevant operation of log collection is executed only when the log collection condition is met, and the problem that the server is heavily loaded due to frequent log collection is avoided.
FIG. 3B schematically shows a flow diagram for detecting whether log collection conditions are met, according to an embodiment of the disclosure.
In this embodiment, the log collection method may include operation S301 and operation S402 described in fig. 3A, in addition to the respective operations described above with reference to fig. 2 and 3A. For the sake of simplicity of description, descriptions of corresponding operations described in fig. 2 and 3A are omitted here. Detecting whether the log collection condition is satisfied may include: detecting whether a log collection request input from outside is received; and/or detecting whether a preset log collection time is reached. That is, detecting whether the log collection condition is satisfied may include at least the following three cases: detecting whether a log collection request input from outside is received or not in case one; detecting whether the preset log collection time is reached or not under the condition II; case three, detecting whether an externally input log collection request is received, and detecting whether a preset log collection time is reached, as shown in fig. 3B, wherein:
in operation S401, it is detected whether an externally input log collection request is received.
In operation S402, it is detected whether a preset log collection time is reached.
In addition, during implementation, whether an externally input log collection request is received or not can be detected in real time or at regular time. The predetermined log collection time may be periodic or aperiodic. Preferably, both log collection conditions are set simultaneously, in which case the event condition is generally given priority over the time condition.
For example, the log file can be collected by presetting the log file at number 1 per month, and if the log mobile phone request sent by the user is detected at number 2 per 8 months, and the log mobile phone request does not meet the preset log collection time, but meets the condition one, the baseboard management controller BMC is triggered to send a log collection command to the disk controller; if No. 8/month 2, the log mobile phone request sent by the user is not detected, and the preset log collection time is not met, so that the baseboard management controller BMC is not triggered to send the log collection command to the disk controller, and the baseboard management controller BMC is not triggered to send the log collection command to the disk controller until No. 1 of the next month.
Through the embodiment of the disclosure, by setting a plurality of trigger modes (request type event trigger mode (also called event condition) and time trigger mode (also called time condition)) for log collection, the technical effects of flexible and various trigger modes and meeting different requirements of users are achieved.
Fig. 3C schematically shows a flow chart of a log collection method according to another embodiment of the present disclosure.
In this embodiment, the log collection method may include operation S501 in addition to operations S201 and S202 described above with reference to fig. 2. The description of operations S201 and S202 is omitted here for the sake of brevity of description. As shown in fig. 3C, wherein:
in operation S501, file description information is predefined in the BMC, where the file description information includes location description information describing locations where the log files are located.
In the embodiment of the present disclosure, before performing each operation in the foregoing embodiment, file description information may be predefined in the BMC, specifically, location description information may be defined in the file description information, where the location information is used to describe a storage location of each log file, and further, operation S201 is performed, which is not described herein again.
It should be understood that the location described by the location description information in the embodiments of the present disclosure includes one or more locations, and is not limited herein.
Through the embodiment of the disclosure, the purpose of collecting the log is achieved on the premise that an operating system does not need to be logged in, a password of the operating system does not need to be input, and the service of the operating system is not influenced.
According to the embodiment of the disclosure, before the BMC sends the log collection command to the disk controller, it is determined whether the designated location is one or more of the locations described by the location description information included in the file description information, and if it is determined that the designated location is not one or more of the locations described by the location description information included in the file description information, the BMC is prohibited from sending the log collection command to the disk controller.
In the embodiment of the disclosure, in order to prevent the disk controller from collecting the logs which need to be kept secret so as to reveal the privacy of the user, the collection authority of the logs needs to be further set, specifically, whether the specified position is one or more of the positions described by the position description information for each log file is judged, and if yes, the BMC is allowed to send a log collection command to the disk controller; otherwise, the BMC is prohibited from sending the log collection command to the disk controller. In other words, other files than the predefined log file prohibit collection.
Through the embodiment of the disclosure, the collection permission of the log is set, namely, the purpose of collecting the log is realized, and the information security is further improved.
Fig. 4 schematically shows a flow chart of a log collection method according to another embodiment of the present disclosure.
As shown in fig. 4, the log collecting method may include operations S601 to S603, in which:
in operation S601, a log collection command sent by the BMC on the server motherboard to the disk controller is received, where the log collection command at least carries indication information for indicating the disk controller to scan a log file in a specified location.
In operation S602, a log file at a designated location is scanned according to the indication of the indication information.
In operation S603, the corresponding scan content will be returned to the BMC.
In an embodiment of the present disclosure, a baseboard management controller is mounted on a server motherboard. The log file, especially the log file of the operating system, may be stored in a designated location (e.g., a C-disk, etc.) of the server, and when the user needs to collect the log file, the baseboard management controller BMC may send a log collection command to the disk controller (for controlling the hard disk/floppy disk, allocating resources, and adjusting data input/output), so that the disk controller completes collection of the log file. However, in order to ensure that the disk controller can quickly find the log file in the server, in the log collection command sent by the BMC received by the disk controller, the command carries at least one indication information that may be used to instruct the disk controller to scan the log file at a specified location in the server (i.e., collect the log file at the specified location). And the disk controller returns the scanning content to the baseboard management controller BMC, the baseboard management controller BMC receives the returned scanning content and stores the scanning content in the corresponding memory, and when a user sends a request for reading the log file, the baseboard management controller BMC executes the operation and further sends the scanning content stored in the memory to the user.
It should be understood that the designated positions in the embodiments of the present disclosure may include one or more, and are not limited herein.
It should be noted that the memory in the embodiment of the present disclosure may be an external storage device for storing the log file alone, or may be one or more memories inside a server for storing the log file, which is not limited herein.
According to the embodiment of the disclosure, the disk controller receives the log collection command sent by the baseboard management controller BMC, and then the disk controller scans the log file and returns the scanning content to the baseboard management controller BMC, so that the purpose of collecting the log is achieved on the premise that an operating system does not need to be logged in, an operating system password does not need to be input, and the service of the operating system is not influenced.
Fig. 5 schematically shows a block diagram of a baseboard management controller BMC according to an embodiment of the present disclosure.
In this embodiment, the baseboard management controller BMC 500 may include a first sending module 510 and a second receiving module 520.
As shown in fig. 5, wherein:
the first sending module 510 is configured to send a log collection command to the disk controller, where the log collection command at least carries indication information for indicating the disk controller to scan a log file at a specified location.
The second receiving module 520 is configured to receive the scanned content returned by the disk controller after the disk controller scans the log file at the specified location according to the indication of the indication information and returns the scanned content.
According to the embodiment of the disclosure, the baseboard management controller BMC sends the log collection command to the disk controller, and then the disk controller scans the log file and returns the scanning content to the baseboard management controller BMC, so that the purpose of collecting the log is achieved on the premise that an operating system does not need to be logged in, an operating system password does not need to be input, and the service of the operating system is not influenced.
Fig. 6A schematically illustrates a block diagram of a baseboard management controller BMC according to another embodiment of the present disclosure.
In this embodiment, the baseboard management controller BMC 500 may include a predefined module 610 in addition to the first sending module 510 and the second receiving module 520 described above with reference to FIG. 5. For simplicity of description, descriptions of the first transmitting module 510 and the second receiving module 520 are omitted herein.
As shown in fig. 6A, the baseboard management controller BMC 500 may include a predefined module 610. Wherein:
the predefined module 610 is configured to predefine file description information in the BMC, where the file description information includes location description information describing locations where the log files are located.
Through the embodiment of the disclosure, the purpose of collecting the log is achieved on the premise that an operating system does not need to be logged in, a password of the operating system does not need to be input, and the service of the operating system is not influenced.
Fig. 6B schematically shows a block diagram of a baseboard management controller BMC according to another embodiment of the present disclosure.
In this embodiment, the baseboard management controller BMC 500 may include a determination module 710 and a permission restriction module 720 in addition to the respective modules described above with reference to FIGS. 5 and 6A. For the sake of simplicity of description, descriptions of the respective modules described in fig. 5 and 6A are omitted here.
As shown in fig. 6B, the BMC 500 may include a determination module 710 and a permission limitation module 720. Wherein:
the determining module 710 is configured to determine whether the specified location is one or more of the locations described by the location description information included in the file description information before the BMC sends the log collection command to the disk controller.
The permission limiting module 720 is configured to prohibit the BMC from sending the log collection command to the disk controller if it is determined that the designated location is not one or more of the locations described by the location description information included in the file description information.
Through the embodiment of the disclosure, the collection permission of the log is set, namely, the purpose of collecting the log is realized, and the information security is further improved.
FIG. 7 schematically shows a block diagram of a disk controller according to an embodiment of the present disclosure.
In this embodiment, the disk controller 600 may include a second receiving module 810, a scanning module 820, and a second transmitting module 830.
As shown in fig. 7, wherein:
the second receiving module 810 is configured to receive a log collection command sent by the BMC on the server motherboard to the disk controller, where the log collection command at least carries indication information for indicating the disk controller to scan a log file in a specified location.
The scanning module 820 is used for scanning the log file at the designated position according to the indication of the indication information.
The second sending module 830 is configured to return the corresponding scanned content to the BMC.
According to the embodiment of the disclosure, the disk controller receives the log collection command sent by the baseboard management controller BMC, and then the disk controller scans the log file and returns the scanning content to the baseboard management controller BMC, so that the purpose of collecting the log is achieved on the premise that an operating system does not need to be logged in, an operating system password does not need to be input, and the service of the operating system is not influenced.
It is understood that the first sending module 510, the second receiving module 520, the pre-defining module 610, the determining module 710, and the permission limiting module 720 may be combined into one module to be implemented, or any one of them may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. It is also understood that the second receiving module 810, the scanning module 820 and the second transmitting module 830 may be combined into one module to be implemented, or any one of them may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present invention, at least one of the first transmitting module 510, the second receiving module 520, the pre-defining module 610, the determining module 710, the permission limiting module 720, the second receiving module 810, the scanning module 820 and the second transmitting module 830 may be at least partially implemented as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or in a suitable combination of three implementations of software, hardware and firmware. Alternatively, at least one of the first transmitting module 510, the second receiving module 520, the pre-defining module 610, the judging module 710, the authority limiting module 720, the second receiving module 810, the scanning module 820 and the second transmitting module 830 may be at least partially implemented as a computer program module, which, when executed by a computer, may perform the functions of the respective modules.
FIG. 8 schematically illustrates a block diagram of a computer system that can implement a log collection method according to an embodiment of the disclosure.
As shown in fig. 8, computer system 700 includes a controller 910 and a memory 920. The computer system 700 may perform the methods described above with reference to fig. 2, 3A-3C, and 4.
Specifically, the controller 910 may include, for example, a baseboard management controller BMC 500 and/or disk controller 600, a general purpose microprocessor, an instruction set processor and/or related chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), and/or the like. The controller 910 may also include onboard memory for caching purposes. The controller 910 may be a single processing unit or a plurality of processing units for performing the different actions of the method flows according to embodiments of the present disclosure described with reference to fig. 2, 3A-3C, and 4.
The memory 920 may be, for example, any medium that can contain, store, communicate, propagate, or transport the instructions. For example, a readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. Specific examples of the readable storage medium include: magnetic storage devices, such as magnetic tape or Hard Disk Drives (HDDs); optical storage devices, such as compact disks (CD-ROMs); a memory, such as a Random Access Memory (RAM) or a flash memory; and/or wired/wireless communication links.
The memory 920 may include a computer program 921, which computer program 921 may include code/computer-executable instructions that, when executed by the controller 910, cause the controller 910 to perform a method flow, such as described above in connection with fig. 2, 3A-3C, and 4, and any variations thereof.
The computer program 921 may be configured with, for example, computer program code comprising computer program modules. For example, in an example embodiment, code in computer program 921 may include one or more program modules, including, for example, module 921A, module 921B, … …. It should be noted that the division and number of modules are not fixed, and those skilled in the art may use suitable program modules or program module combinations according to actual situations, when these program modules are executed by the controller 910, the controller 910 may execute the method flows described above in conjunction with fig. 2, 3A to 3C and 4, and any variation thereof.
Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.
While the disclosure has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents. Accordingly, the scope of the present disclosure should not be limited to the above-described embodiments, but should be defined not only by the appended claims, but also by equivalents thereof.

Claims (10)

1. A log collection method, comprising:
generating a log collection command, wherein the log collection command at least carries indication information for indicating a disk controller to scan a log file at a specified position;
before sending the log collection command to a disk controller through a Baseboard Management Controller (BMC) on a server mainboard, judging whether the specified position is one or more of positions described by position description information contained in file description information;
in response to the specified location being one or more of the locations described by the location description information contained in the file description information, sending the log collection command to the disk controller; and
and after the disk controller scans the log file at the specified position according to the indication of the indication information and returns the scanning content, receiving the scanning content returned by the disk controller through the BMC.
2. The method of claim 1, wherein sending the log collection command to the disk controller by a Baseboard Management Controller (BMC) on the server motherboard comprises:
detecting whether log collection conditions are met; and
and if the log collection condition is detected to be met, triggering the BMC to send the log collection command to the disk controller.
3. The method of claim 2, wherein detecting whether a log collection condition is satisfied comprises:
detecting whether a log collection request input from outside is received; and/or
Whether the preset log collection time is reached is detected.
4. The method of any of claims 1-3, wherein the method further comprises:
and predefining the file description information in the BMC, wherein the file description information comprises the position description information which describes the position of each log file.
5. The method of claim 1, wherein the method further comprises:
in response to the specified location not being one or more of the locations described by the location description information contained in the file description information, inhibiting the BMC from sending the log collection command to the disk controller.
6. A log collection method, comprising:
receiving a log collection command sent by a Baseboard Management Controller (BMC) on a server mainboard to a disk controller, wherein the log collection command at least carries indication information for indicating the disk controller to scan a log file on a specified position;
before receiving the log collection command, responding to the log collection command that the designated position is one or more of the positions of the position description information contained in the file description information after the judgment of a Baseboard Management Controller (BMC) whether the designated position is one or more of the positions described by the position information contained in the file description information; scanning the log file at the designated position according to the indication of the indication information; and
and returning the corresponding scanning content to the BMC.
7. A Baseboard Management Controller (BMC) is arranged on a server mainboard and used for collecting logs, and the BMC comprises:
the generating module is used for generating a log collecting command, wherein the log collecting command at least carries indication information for indicating the disk controller to scan the log file on the specified position;
the judging module is used for judging whether the specified position is one or more of the positions described by the position description information contained in the file description information before the substrate management controller BMC on the server mainboard sends the log collecting command to the disk controller;
a first sending module, configured to send a log collection command to a disk controller in response to the specified location being one or more of locations described by location description information included in the file description information; and
and the second receiving module is used for receiving the scanning content returned by the disk controller after the disk controller scans the log file at the specified position according to the indication of the indication information and returns the scanning content.
8. The BMC of claim 7, wherein the BMC further comprises:
and the pre-defining module is used for pre-defining file description information in the BMC, wherein the file description information comprises position description information for describing the positions of the log files.
9. The BMC of claim 8, wherein the BMC further comprises:
and the permission limiting module is used for prohibiting the BMC from sending the log collection command to the disk controller under the condition that the specified position is judged not to be one or more of the positions described by the position description information contained in the file description information.
10. A disk controller for performing log collection, comprising:
the second receiving module is used for receiving a log collection command sent by a baseboard management controller BMC on a server mainboard to a disk controller, wherein the log collection command at least carries indication information used for indicating the disk controller to scan a log file on a specified position;
before receiving the log collection command, responding to the log collection command that the designated position is one or more of the positions of the position description information contained in the file description information after the judgment of a Baseboard Management Controller (BMC) whether the designated position is one or more of the positions described by the position information contained in the file description information;
the scanning module is used for scanning the log file on the designated position according to the indication of the indication information; and
and the second sending module is used for returning the corresponding scanning content to the BMC.
CN201710811006.0A 2017-09-08 2017-09-08 Log collection method, Baseboard Management Controller (BMC) and disk controller Active CN107608868B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710811006.0A CN107608868B (en) 2017-09-08 2017-09-08 Log collection method, Baseboard Management Controller (BMC) and disk controller

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710811006.0A CN107608868B (en) 2017-09-08 2017-09-08 Log collection method, Baseboard Management Controller (BMC) and disk controller

Publications (2)

Publication Number Publication Date
CN107608868A CN107608868A (en) 2018-01-19
CN107608868B true CN107608868B (en) 2021-10-22

Family

ID=61062476

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710811006.0A Active CN107608868B (en) 2017-09-08 2017-09-08 Log collection method, Baseboard Management Controller (BMC) and disk controller

Country Status (1)

Country Link
CN (1) CN107608868B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108777638A (en) * 2018-08-27 2018-11-09 郑州云海信息技术有限公司 A kind of server log information backup method and system
CN116881091B (en) * 2023-09-08 2024-05-28 深圳云豹智能有限公司 System event log reporting method, device, chip, equipment and storage medium

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4606273B2 (en) * 2004-08-30 2011-01-05 株式会社リコー Log collection device, log collection program
CN104268068A (en) * 2014-09-24 2015-01-07 浪潮电子信息产业股份有限公司 Method for acquiring server log information
JP6356075B2 (en) * 2015-01-07 2018-07-11 株式会社日立製作所 Log collection system and log collection method
CN105224436A (en) * 2015-10-29 2016-01-06 曙光信息产业股份有限公司 A kind of operation condition of server method for supervising and device
CN106021064A (en) * 2016-05-16 2016-10-12 浪潮电子信息产业股份有限公司 Monitoring information collection method, baseboard management controller and system
CN106951352A (en) * 2017-03-13 2017-07-14 郑州云海信息技术有限公司 A kind of server log memory management method
CN107025166B (en) * 2017-04-27 2020-12-22 上海联影医疗科技股份有限公司 Log collection method and system

Also Published As

Publication number Publication date
CN107608868A (en) 2018-01-19

Similar Documents

Publication Publication Date Title
US20170155684A1 (en) Enforcement of proximity based policies
US20160378691A1 (en) System, apparatus and method for protecting a storage against an attack
US20170134405A1 (en) Dynamic Honeypot System
US20130152169A1 (en) Controlling access to resources on a network
US20060294596A1 (en) Methods, systems, and apparatus to detect unauthorized resource accesses
US10956383B2 (en) Device backup and wipe
US20160004648A1 (en) Data erasing apparatus, data erasing method, and computer-readable storage medium
US10509704B2 (en) System and method for automatic data backup based on multi-factor environment monitoring
CN110134700B (en) Data uplink method, device, computer equipment and storage medium
CN107608868B (en) Log collection method, Baseboard Management Controller (BMC) and disk controller
US20150213281A1 (en) Method of configuring permission for sharing data and touch link electronic device utilizing the same
US11416601B2 (en) Method and system for improved data control and access
US10339307B2 (en) Intrusion detection system in a device comprising a first operating system and a second operating system
CN102763113A (en) Method and apparatus to reset platform configuration register in mobile trusted module
CN109818972B (en) Information security management method and device for industrial control system and electronic equipment
CN108040122B (en) File transmission method and device
US20150370482A1 (en) Storage apparatus, communication apparatus, and storage control system
US10242191B2 (en) Dynamically-loaded code analysis device, dynamically-loaded code analysis method, and dynamically-loaded code analysis program
US20230281288A1 (en) Server that supports security access of terminal device of the user and controlling method thereof
CN113821841B (en) Resource management method, computing device and readable storage medium
US20160373464A1 (en) Communication system, method and base station
KR102310321B1 (en) Method and apparatus for providing web page using captive portal
CN110839201B (en) Pipeline data processing method, transmitting device, receiving device and storage medium
RU2016148424A (en) METHOD OF MANAGEMENT, DEVICE FOR CONTROL CONTACT IN THE TERMINAL AND TERMINAL
KR101980487B1 (en) Usb device for network security

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
GR01 Patent grant
GR01 Patent grant