A CPLD-based server exception log management method

Abstract

This invention provides a server anomaly log management method based on CPLD, relating to the field of computer server technology. The method includes: the server CPU generating logs in real time and transmitting them transparently to the BMC via CPLD; the CPLD mirroring the logs and analyzing anomalies, outputting a service anomaly log; the CPLD storing the logs in EEPROM; upon receiving a BMC access request, the CPLD switching EEPROM permissions to the BMC; after the BMC access ends, a termination command is sent to the CPLD; and the CPLD revoking the BMC's access permissions to the EEPROM. This addresses the technical problems of insufficient real-time performance in existing server anomaly log storage methods, leading to easy loss of anomaly information and excessive BMC resource overhead, thus affecting server operating efficiency. The method achieves the technical effect of CPLD monitoring and storing server serial port logs, reducing BMC overhead, and improving server operating efficiency.

Description

Technical Field

[0001] This invention relates to the field of computer server technology, and specifically to a server exception log management method based on CPLD. Background Technology

[0002] With the continuous expansion of server application scenarios and the growth of business demands, server stability has become particularly important. Servers may experience abnormal situations during operation due to hardware failures, software anomalies, or external environmental influences. To improve server maintainability and fault diagnosis efficiency, the recording and management of server anomaly logs are crucial.

[0003] Server anomaly logs typically only occur at the moment a server anomaly occurs. If administrators fail to view them in real time or the logs are not stored promptly, critical anomaly information may be lost, impacting fault location and repair efficiency. Therefore, server products generally employ various measures to preserve anomaly logs for analysis and diagnosis after a fault occurs.

[0004] However, existing server anomaly log management solutions have certain limitations. For example, some solutions rely on the Baseboard Management Controller (BMC) to monitor server CPU logs in real time, but the BMC itself has limited resources. Continuous high-frequency collection and storage of logs will consume a large amount of system resources, affecting the normal operation of the server. In addition, the real-time performance of log storage in some solutions is insufficient, which may result in some critical anomaly information not being recorded, affecting the tracing and analysis of problems.

[0005] To address the aforementioned issues, this invention proposes a server anomaly log management method based on CPLD (Complex Programmable Lock Device). By leveraging the high real-time performance and low resource overhead of CPLD, it achieves accurate capture and efficient storage of server anomaly logs, while reducing the resource consumption of BMC and improving the overall operating efficiency and maintenance capabilities of the server. Summary of the Invention

[0006] This application provides a CPLD-based server exception log management method to address the technical problems of insufficient real-time performance of existing server exception log storage methods, which easily leads to the loss of exception information and excessive BMC resource overhead, thereby affecting server operating efficiency. The method enables CPLD monitoring and storage of server serial port logs, improving real-time performance, ensuring complete recording of exception logs, and reducing BMC overhead, thereby improving server operating efficiency.

[0007] In view of the above problems, this application provides a server exception log management method based on CPLD. The method includes: the server CPU generating server logs in real time and transmitting the server logs to the BMC through the CPLD; the CPLD synchronously mirroring a copy of the server logs and outputting a service exception log by performing exception analysis on the copy data; the CPLD storing the service exception logs in EEPROM; after receiving an exception log access request instruction sent by the BMC, the CPLD switching the access permission of the EEPROM to the BMC; after the BMC finishes accessing the EEPROM, it sends an exception log access termination instruction to the CPLD; after receiving the exception log access termination instruction sent by the BMC, the CPLD revoking the BMC's access permission to the EEPROM.

[0008] One or more technical solutions provided in this application have at least the following technical effects or advantages:

[0009] This application provides a server exception log management method based on CPLD, which relates to the field of computer server technology. It solves the technical problems of insufficient real-time performance of existing server exception log storage methods, which easily leads to the loss of exception information and excessive BMC resource overhead, thereby affecting server operating efficiency. The method realizes CPLD monitoring and storage of server serial port logs, improves real-time performance, ensures complete recording of exception logs, and reduces BMC overhead, thereby improving server operating efficiency. Attached Figure Description

[0010] Figure 1 This application provides a schematic diagram of a server exception log management method based on CPLD.

[0011] Figure 2 This application provides a schematic diagram of the process for switching the access permissions of EEPROM to BMC in a server exception log management method based on CPLD. Detailed Implementation

[0012] This application provides a CPLD-based server exception log management method to address the technical problems of insufficient real-time performance in existing server exception log storage methods, which easily leads to the loss of exception information and excessive BMC resource overhead, thus affecting server operating efficiency. The method enables CPLD monitoring and storage of server serial port logs, improving real-time performance, ensuring complete recording of exception logs, and reducing BMC overhead, thereby improving server operating efficiency.

[0013] Examples, such as Figure 1As shown in the figure, this application provides a server exception log management method based on CPLD, the method including:

[0014] Step S100: The server CPU generates server logs in real time and transmits the server logs to the BMC via the CPLD.

[0015] Specifically, during server operation, its Central Processing Unit (CPU) generates server logs in real time. These logs record the server's operating status, event information, and potential anomalies. To ensure the real-time nature and integrity of the logs, the server CPU transmits the generated logs directly to the Baseboard Management Controller (BMC) via a Complex Programmable Logic Device (CPLD). The CPLD establishes a direct transmission path, acting as an intermediary bridge. It does not process or modify the log data but transmits it intact to the BMC, ensuring the BMC receives the log information generated by the server CPU in real time. This transmission mechanism not only improves log transmission efficiency but also avoids the loss of critical information due to log processing delays.

[0016] Furthermore, step S100 of this application also includes:

[0017] Step S110: The CPLD switches the log serial port sending end of the server CPU to the log serial port receiving end of the BMC, forming a direct pass-through path; Step S120: By real-time mirroring the log data stream flowing through the CPLD, a copy of the log synchronized with the server log is obtained.

[0018] Specifically, the CPLD, through its hardware connectivity, directly connects the server CPU's log serial port sender (log output) to the BMC's log serial port receiver (log input) by default, forming a transparent transmission path. Specifically, the CPLD connects to the server CPU's log output via the first serial port and to the BMC's serial port receiver via the second serial port, thus constructing a complete serial data path. This direct transmission path allows log data generated by the server CPU to be directly transmitted to the BMC via the CPLD without additional processing or storage, ensuring real-time and efficient log transmission. Furthermore, while transmitting log data, the CPLD also performs real-time mirroring on the log data stream flowing through it. This mirroring operation generates a copy of the log data that is completely synchronized with the server logs. This copy can be used for subsequent anomaly analysis or other processing operations. In this way, CPLD not only achieves efficient log pass-through, but also provides a reliable data source for log backup and analysis, further enhancing the flexibility and reliability of log management.

[0019] Step S200: The CPLD synchronously mirrors the server log copy data and outputs a service exception log by performing anomaly analysis on the copy data.

[0020] Specifically, while the CPLD transmits the log data generated by the server CPU to the BMC, it also performs a synchronized mirroring of the log data, generating a copy that is completely identical to the original log data. This copy is kept in real-time synchronized with the server logs to ensure the integrity and accuracy of its content. Subsequently, the CPLD performs anomaly analysis on these copies of the data. Specifically, CPLD performs real-time detection and matching of replica data based on predefined anomaly characteristics, such as specific error codes (Error Code 500, indicating an internal server error; Error Code 0x80004005, indicating a hardware device or driver initialization failure), abnormal states (CPU Overheating, indicating the CPU temperature exceeds a safe threshold; FanFailure, indicating abnormal server fan speed or shutdown), or log modes (Kernel Panic-Not Syncing: Fatal exception, indicating an operating system kernel crash; Connection timeout after 30 seconds, indicating a network connection timeout). If it finds content matching the anomaly characteristics in the log data, CPLD captures this data and records it in the anomaly log. These anomaly logs record the faults or abnormal events that occur during server operation, providing crucial information for subsequent fault diagnosis and maintenance. Through this mechanism, CPLD not only achieves real-time transparent transmission of log data but also quickly identifies and extracts anomaly information from the log stream, ensuring that administrators can promptly obtain information about problems in server operation, thereby improving the efficiency and accuracy of fault diagnosis.

[0021] Furthermore, step S200 also includes:

[0022] Step S210: Pre-configure a FIFO buffer in the CPLD, wherein the FIFO buffer is used to temporarily store the copy data of the server log; Step S220: Real-time detection of whether the copy data of the server log in the FIFO buffer conforms to predefined abnormal characteristics; Step S230: If the copy data of the server log does not conform to the predefined abnormal characteristics, then continuously pass the server log to the BMC; Step S240: If the copy data of the server log conforms to the predefined abnormal characteristics, then trigger a data capture operation; Step S250: Capture the service abnormal log through the data capture operation, and write the service abnormal log to the EEPROM.

[0023] Specifically, a FIFO (First In First Out) buffer is pre-configured in the CPLD. This buffer is used to temporarily store copies of server log data. The FIFO buffer design ensures the orderly storage and retrieval of log data, avoiding data loss or corruption. The CPLD monitors the log copy data in the FIFO buffer in real time to determine whether it conforms to predefined anomaly characteristics (such as specific error codes, abnormal states, or log patterns). The detection process is as follows: The CPLD starts from the head of the FIFO buffer and reads the log data sequentially. It compares the read log data with predefined anomaly characteristics in the anomaly characteristic library, checks whether the log contains specific error codes, detects whether keywords of abnormal states appear in the log, and uses pattern matching algorithms (such as regular expressions) to determine whether the log conforms to predefined anomaly patterns. If no anomaly characteristics are found in the log copy data, the CPLD will continue to pass the log data through to the BMC, while clearing the processed data in the FIFO buffer to make room for new logs. Conversely, if content conforming to predefined anomaly characteristics is detected in the log copy data, the CPLD will immediately trigger a data capture operation. During data capture, the CPLD extracts exception log data from the FIFO buffer, including the log that triggered the exception and related logs before and after it (e.g., the first 512 bytes and the last 2048 bytes), ensuring the integrity of the exception context. This is then written as a service exception log to EEPROM (Electrically Erasable Programmable Read-Only Memory). As a non-volatile storage medium, EEPROM can retain these exception logs long-term, ensuring data integrity even during server power outages. Through this mechanism, the CPLD can not only monitor log data in real time but also quickly capture and store critical information when an exception is detected, providing reliable data support for subsequent fault diagnosis and maintenance. Simultaneously, the use of the FIFO buffer ensures efficient processing and storage of log data, avoiding data loss or delays.

[0024] Furthermore, step S210 of this application includes:

[0025] Step S211: The capacity of the FIFO buffer is 512 bytes.

[0026] Specifically, the FIFO buffer is designed with a capacity of 512 bytes to ensure sufficient storage space to cache log content as log data flows through the CPLD, enabling real-time analysis and anomaly detection. When log data generated by the server CPU flows through the CPLD, the CPLD writes this data sequentially into the FIFO buffer until it is full. If the buffer is full, new data overwrites the oldest data, ensuring that the latest log information is always stored in the buffer. The 512-byte capacity is designed to balance storage efficiency and real-time performance. 512 bytes is sufficient to store log data within a certain time range, ensuring that enough information can be captured when anomalies are detected. Furthermore, the smaller buffer capacity reduces data processing and retrieval latency, allowing the CPLD to quickly respond to changes in the log data stream and promptly detect anomalies. Through this design, the FIFO buffer can provide reliable data support for the capture and analysis of anomaly logs while ensuring real-time log data processing.

[0027] Furthermore, step S250 includes:

[0028] Step S251: Calculate the write start address based on the circular address pointer of the EEPROM ring storage area; Step S252: Write the 512 bytes of log data cached in the FIFO buffer before the data capture operation is triggered as the first abnormal log segment into the storage area corresponding to the write start address in the EEPROM; Step S253: Capture the serial port data stream sent by the log serial port transmitter after the data capture operation is triggered in real time, and write the subsequent 2048 bytes of log data as the second abnormal log segment into the storage area; Step S254: Wherein, the first abnormal log segment and the second abnormal log segment constitute the complete service abnormal log in the EEPROM.

[0029] Specifically, the EEPROM employs a circular buffer design, which manages the data write position using a circular address pointer. When new log data needs to be written, the CPLD calculates the current write start address based on the current value of the circular address pointer, ensuring that data is stored in the EEPROM in an orderly manner. Before the data capture operation is triggered, 512 bytes of log data are already cached in the FIFO buffer. This data is used as the first exception log segment and written to the storage area in the EEPROM corresponding to the write start address. After the data capture operation is triggered, the CPLD captures the serial data stream sent by the log serial port transmitter in real time and writes the subsequent 2048 bytes of log data as the second exception log segment to the EEPROM's storage area. The first exception log segment (512 bytes) and the second exception log segment (2048 bytes) together constitute a complete service exception log in the EEPROM. This segmented storage method ensures the integrity of the exception log, including both critical log information before the exception occurred and detailed data after the exception. Through the design of the circular storage area and the management of the circular address pointer, the EEPROM can efficiently store large amounts of log data while avoiding waste of storage space. This mechanism not only improves the flexibility of log storage but also provides comprehensive and reliable data support for subsequent fault analysis and diagnosis.

[0030] Step S300: The CPLD saves the service exception log in EEPROM.

[0031] Specifically, after detecting abnormal characteristics in the server logs, the CPLD performs a data capture operation and stores the captured abnormal log data into the EEPROM. During this process, the CPLD first writes the log data already cached in the FIFO before the anomaly occurred into the EEPROM, and then continues to record the log data after the anomaly occurs in real time, appending it to the EEPROM to ensure the integrity of the abnormal logs. By storing the abnormal logs in the EEPROM, the log data remains available even after the server is powered off or restarted, providing administrators with reliable data for server fault analysis.

[0032] Step S400: After receiving the abnormal log access request instruction sent by the BMC, the CPLD switches the access permission of the EEPROM to the BMC.

[0033] Specifically, when the CPLD receives an exception log access request command from the BMC, it performs the following operations to switch the EEPROM access permissions to the BMC: First, the BMC sends the exception log access request command to the CPLD via the I2C interface (Inter-Integrated Circuit, a serial communication protocol), requesting to read the service exception log stored in the EEPROM. Upon receiving the request command, the CPLD outputs a control signal to drive the I2CSwitch (I2C switch) to switch the EEPROM access path. After the access permission switch is complete, the BMC can read the exception log data in the EEPROM through the I2C interface. Through this mechanism, the CPLD achieves dynamic management of EEPROM access permissions, ensuring that the BMC can only access the exception log data when needed, while at other times the CPLD has exclusive control, thereby guaranteeing the security of the log data and the stability of the system.

[0034] Furthermore, such as Figure 2 As shown, step S400 includes:

[0035] Step S410: When the BMC needs to query the server's exception log, the BMC sends the exception log access request instruction to the CPLD through the first I2C interface connected to the CPLD; Step S420: After receiving the exception log access request instruction, the CPLD outputs a first control signal through the CPLD's GPIO pin; Step S430: The first control signal drives the I2C switch to connect the communication path from the BMC to the EEPROM, wherein the I2C switch is used to switch the access permissions of the EEPROM.

[0036] Specifically, when the BMC needs to query the server exception log, it sends an exception log access request command to the CPLD through the first I2C interface connected to the CPLD. First, the BMC sends this command to the CPLD via the first I2C interface, requesting access to the service exception log stored in the EEPROM. Upon receiving the access request command from the BMC, the CPLD outputs a first control signal through its GPIO pin (General Purpose Input / Output). This control signal drives the I2C switch to change the EEPROM access path. Upon receiving the first control signal, the I2C switch establishes the communication path from the BMC to the EEPROM while simultaneously disconnecting the communication path from the CPLD to the EEPROM. This allows the BMC to directly access the exception log data in the EEPROM via the I2C interface. Through the I2C switch switching, the EEPROM access permission is transferred from the CPLD to the BMC. The BMC can then read the header information in the EEPROM to understand the log's storage structure and location, and then read the specific exception log content based on the header information. Through this mechanism, CPLD achieves dynamic management of EEPROM access permissions, ensuring that BMC can only access abnormal log data when needed, while at other times it is exclusively controlled by CPLD, thereby guaranteeing the security of log data and the stability of the system.

[0037] Furthermore, step S430 also includes:

[0038] Step S431: The BMC reads the header information of the EEPROM; Step S432: Reads the server exception log according to the header information; Step S433: Performs log management operations on the server exception log in the EEPROM through the web interface of the BMC, wherein the log management operations include, but are not limited to, deletion.

[0039] Specifically, when the BMC accesses the EEPROM via the I2C interface, it first reads the header information in the EEPROM. This header information records the location and content of the log data stored in the EEPROM, such as the log's start address, length, and timestamp. This information helps the BMC quickly locate and parse specific exception log data. After obtaining the header information, the BMC reads the Service Exception Log based on the records within it. This log data includes detailed information before and after the exception occurred, providing crucial information for fault diagnosis. After reading, the BMC provides exception log management functions through its web interface. Server administrators can perform various log management operations through the web interface, such as deleting logs (cleaning up old log data in the EEPROM to free up storage space), marking processed logs as read for later tracking, and marking important exception logs as favorites for quick retrieval and analysis. In this way, the BMC not only efficiently reads and manages exception logs in the EEPROM but also provides server administrators with a convenient interface, improving the flexibility and efficiency of log management.

[0040] Furthermore, step S430 also includes:

[0041] Step S434: The I2C Switch has a second I2C interface connected to the CPLD, a third I2C interface connected to the BMC, and a common I2C interface connected to the EEPROM.

[0042] Specifically, an I2C switch is a hardware device used for switching communication paths. It has four key I2C interfaces: The first is the first I2C interface, connecting the BMC and CPLD. This interface is used by the BMC to send exception log access request commands to the CPLD and receive responses from the CPLD. This interface is the direct communication channel between the BMC and CPLD, used to coordinate the switching of EEPROM access permissions. The second is the second I2C interface, connecting the CPLD. This interface is used for communication between the CPLD and the I2C switch, enabling the CPLD to control the switching operation of the I2C switch. The third is the third I2C interface, connecting the BMC. This interface is used for communication between the BMC and the I2C switch, allowing the BMC to access the EEPROM through the I2C switch when needed. The fourth is the common I2C interface, connecting the EEPROM. This interface is the only communication path between the I2C switch and the EEPROM, used for transmitting log data. The I2C switch dynamically switches EEPROM access permissions based on the CPLD's control signals. When the CPLD needs to access the EEPROM, the I2C switch connects the common I2C interface to the second I2C interface, allowing the CPLD to directly read and write data in the EEPROM. When the BMC needs to access the EEPROM, the CPLD drives the I2C switch to switch the common I2C interface to the third I2C interface via control signals, enabling the BMC to read exception log data in the EEPROM. Through this design, the I2C switch achieves flexible management of EEPROM access permissions, ensuring that the CPLD and BMC can access the EEPROM separately without conflict, thereby improving system security and efficiency.

[0043] Step S500: After the BMC finishes accessing the EEPROM, it sends an exception log access termination command to the CPLD.

[0044] Specifically, after the BMC completes its access to the EEPROM, it sends an exception log access termination command to the CPLD via the first I2C interface. First, the BMC accesses the EEPROM through the I2C switch to read the necessary exception log data, including header information and the actual log content. After completing log reading or other management operations (such as deletion or marking), the BMC prepares to release its access rights to the EEPROM. At this point, the BMC sends an exception log access termination command to the CPLD via the first I2C interface, notifying the CPLD that its access operation has ended. This command is a predefined signal used to trigger the CPLD to perform subsequent permission revocation operations. Through this mechanism, the BMC can promptly release permissions after completing its access to the EEPROM, ensuring the CPLD's exclusive control over the EEPROM, thereby guaranteeing the security of log data and the stability of the system.

[0045] Step S600: After receiving the abnormal log access termination instruction sent by the BMC, the CPLD revoked the BMC's access rights to the EEPROM.

[0046] Specifically, when the CPLD receives an abnormal log access termination command from the BMC, it performs the following operations to revoke the BMC's access rights to the EEPROM. First, the BMC sends the abnormal log access termination command to the CPLD via the first I2C interface, notifying the CPLD that its access operation has ended. Upon receiving the termination command, the CPLD outputs a second control signal via its GPIO pin. Upon receiving this second control signal, the I2C switch switches the EEPROM's communication path from the BMC back to the CPLD, restoring the EEPROM's access rights to the CPLD. This prevents the BMC from directly accessing the data in the EEPROM, allowing the CPLD to regain exclusive control over the EEPROM, ensuring the security of log data and the stability of the system. Through this mechanism, the CPLD can dynamically manage EEPROM access rights, ensuring that the BMC can only access log data when needed, and promptly revoking access after access is completed, avoiding unnecessary resource consumption and security risks.

[0047] Furthermore, step S600 also includes:

[0048] Step S610: When the BMC finishes querying the server's abnormal log, the BMC sends the abnormal log access termination instruction to the CPLD through the first I2C interface; Step S620: After receiving the abnormal log access termination instruction, the CPLD outputs a second control signal through the CPLD's GPIO pin; Step S630: The second control signal drives the I2CSwitch to restore the communication path from the CPLD to the EEPROM.

[0049] Specifically, after the BMC completes its query of the server's exception logs, it sends an exception log access termination command to the CPLD via the first I2C interface, notifying the CPLD that its access operation has ended. During this process, the BMC sends the exception log access termination command to the CPLD via the first I2C interface, indicating that it has completed reading log data or performing other operations on the EEPROM. Upon receiving the termination command, the CPLD outputs a second control signal through its GPIO pin. This signal drives the I2CSwitch (I2C switch) to switch the EEPROM access path. Upon receiving the second control signal, the I2C switch disconnects the BMC from the EEPROM and restores the communication path between the CPLD and the EEPROM. This operation ensures that only the CPLD can access the log information in the EEPROM, and the BMC can no longer directly read or manipulate the data in the EEPROM. After the switch is complete, the CPLD regains exclusive access to the EEPROM, ensuring the security of the log data and the stability of the system. This mechanism avoids resource conflicts or security issues that might arise from the BMC occupying EEPROM access permissions for an extended period, thereby reducing BMC overhead and improving server operating efficiency.

[0050] In summary, the server anomaly log management method based on CPLD provided in this application embodiment has at least the following technical effects: enabling CPLD monitoring and storage of server serial port logs, improving real-time performance, ensuring complete recording of anomaly logs, and reducing BMC overhead to improve server operating efficiency.

[0051] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A server exception log management method based on CPLD, characterized in that, The method includes: The server CPU generates server logs in real time, and the server logs are transparently transmitted to the BMC via the CPLD; The CPLD synchronously mirrors the server logs and outputs service exception logs by performing anomaly analysis on the mirrored data. The CPLD stores the service exception log in EEPROM; After receiving the abnormal log access request instruction sent by the BMC, the CPLD switches the access permission of the EEPROM to the BMC; After accessing the EEPROM, the BMC sends an exception log access termination command to the CPLD. After receiving the abnormal log access termination instruction sent by the BMC, the CPLD revoked the BMC's access rights to the EEPROM. The server CPU generates server logs in real time and transmits these logs to the BMC via the CPLD, including: The CPLD switches the log serial port sending end of the server CPU to the log serial port receiving end of the BMC, forming a direct transparent transmission path. By mirroring the log data stream flowing through the CPLD in real time, a replica of the log data synchronized with the server log is obtained; The CPLD synchronously mirrors the server logs, and outputs service exception logs by performing anomaly analysis on the mirrored data, including: The CPLD is pre-configured with a FIFO buffer, wherein the FIFO buffer is used to temporarily store a copy of the server log data; Real-time detection of whether the copy data of the server log in the FIFO buffer conforms to predefined abnormal characteristics; If the replica data of the server log does not conform to the predefined abnormal characteristics, the server log will be continuously passed through to the BMC; If the copy data of the server log matches the predefined abnormal characteristics, a data capture operation is triggered; The service exception log is captured through the data capture operation and written to the EEPROM.

2. The server exception log management method based on CPLD as described in claim 1, characterized in that, After receiving an exception log access request instruction sent by the BMC, the CPLD switches the access permission of the EEPROM to the BMC, including: When the BMC needs to query the server exception log, the BMC sends the exception log access request instruction to the CPLD through the first I2C interface connected to the CPLD. Upon receiving the abnormal log access request instruction, the CPLD outputs a first control signal through the CPLD's GPIO pin. The first control signal drives the I2C switch to establish the communication path from the BMC to the EEPROM, wherein the I2C switch is used to switch the access permissions of the EEPROM.

3. The server exception log management method based on CPLD as described in claim 2, characterized in that, After establishing the communication path from the BMC to the EEPROM by controlling the I2C switch via GPIO, the following steps are also included: The BMC reads the header information of the EEPROM; Read the server exception log based on the header information; The BMC's web interface is used to perform log management operations on the server exception logs in the EEPROM, including but not limited to deletion.

4. The server exception log management method based on CPLD as described in claim 2, characterized in that, After receiving an exception log access termination command from the BMC, the CPLD revoks the BMC's access rights to the EEPROM, including: When the BMC finishes querying the server's exception log, the BMC sends the exception log access termination command to the CPLD through the first I2C interface. After receiving the abnormal log access termination instruction, the CPLD outputs a second control signal through the CPLD's GPIO pin; The second control signal drives the I2C switch to restore the communication path from the CPLD to the EEPROM.

5. The server exception log management method based on CPLD as described in claim 1, characterized in that, The FIFO buffer has a capacity of 512 bytes.

6. The server exception log management method based on CPLD as described in claim 2, characterized in that, The I2C switch has a second I2C interface for connecting to the CPLD, a third I2C interface for connecting to the BMC, and a common I2C interface for connecting to the EEPROM.

7. The server exception log management method based on CPLD as described in claim 1, characterized in that, The capture of the service exception logs through the data capture operation includes: Calculate the write start address based on the circular address pointer of the EEPROM ring memory area; Before the data capture operation is triggered, 512 bytes of log data cached in the FIFO buffer are written as the first abnormal log segment to the storage area in the EEPROM corresponding to the write start address. After the data capture operation is triggered in real time, the serial port data stream sent by the log serial port sending end will have the subsequent 2048 bytes of log data in the serial port data stream written into the storage area as the second abnormal log segment. The first and second exception log segments together constitute the complete service exception log in the EEPROM.

Images