Server alarm method and device, computer equipment and storage medium

Abstract

The invention relates to the technical field of computers, and discloses a server alarm method and device, computer equipment and a storage medium, and the method comprises the steps: obtaining and storing an alarm message configuration file from a user management end; and under the condition that the server has a fault, determining an alarm parameter and a message sending sequence corresponding to the alarm parameter according to the alarm message configuration file, obtaining an alarm message corresponding to the alarm parameter, sending the alarm message to a user management end according to the message sending sequence, and indicating the user management end to display the alarm message. The problems that sent alarm messages are not suitable for application scenes of all clients, parameters needed by the clients cannot be reserved, and the alarm messages cannot be sent according to a formulated sequence are solved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a server alarm method, device, computer equipment and storage medium. Background Art

[0002] Server clusters are important infrastructure for data storage and monitoring, and their performance and stability are particularly important. SNMP (Simple Network Management Protocol) trap alarms are a common and efficient alarm method that is widely used in server cluster monitoring systems. When the BMC (Board Management Controller) management end detects an abnormality in server equipment or functions, the trap alarm mechanism will be triggered immediately. The BMC will determine the abnormal information based on the key information fields in the server log, and according to the format requirements of the trap message, encapsulate the abnormal information into a trap alarm message, and actively send the trap alarm message to the user management end, so that users can understand the health status of the server equipment in real time, and respond and handle problems quickly when they occur.

[0003] Through the SNMPtrap alarm mechanism, management users can monitor the device health information of the server cluster in real time, such as CPU (Central Processing Unit) usage, memory occupancy, etc. Once an abnormality is found, they can immediately receive the trap alarm message sent by the BMC and take corresponding measures to deal with it. However, the variable attribute parameter configuration of the SNMPtrap alarm mechanism has been set and completed in the BMC source code stage. Therefore, when the BMC management end issues an alarm, the OID (Object Identifier) ​​parameter in the trap alarm message received by the user management end strictly follows the queue order preset by the developer, and the user cannot directly modify these parameter configurations to ensure the stability and consistency of the system. However, there are many OID parameters and they are not suitable for all customer application scenarios. Therefore, customers will make customized requirements for the SNMPtrap alarm mechanism. They only need to retain the required OID parameters and send trap alarm messages in a specific order. Multiple customers may have different requirements for this, which increases the manpower investment of developers and increases the company's investment.

[0004] Therefore, the related technology has the problem that the alarm message sent is not suitable for all customer application scenarios, and it is impossible to retain the parameters required by the customer and send the alarm message in a specified order. Summary of the invention

[0005] In view of this, the present invention provides a server alarm method, device, computer equipment and storage medium to solve the problem that the sent alarm message is not suitable for all customer application scenarios, cannot retain the parameters required by the customer and send the alarm message in a specified order.

[0006] In a first aspect, the present invention provides a server alarm method, which is applied to a baseboard management controller, comprising:

[0007] Obtain and save the alarm message configuration file from the user management terminal;

[0008] In the event of a server failure, the alarm parameters and the message sending order corresponding to the alarm parameters are determined according to the alarm message configuration file, the alarm message corresponding to the alarm parameters is obtained, and the alarm message is sent to the user management end according to the message sending order, instructing the user management end to display the alarm message.

[0009] The server alarm method provided in this embodiment, in the event of a server failure, determines the alarm parameters and the message sending order according to the alarm message configuration file sent by the user management end, obtains the alarm message corresponding to the alarm parameter, and sends the alarm message to the user management end according to the message sending order. The user can adjust the alarm parameters and message sending order contained in the alarm message configuration file to meet diverse application requirements. The alarm message sent by the baseboard management controller can accurately match and fully meet the diverse needs of customers. It solves the problem that the alarm message sent is not applicable to all customer application scenarios, and it is impossible to retain the parameters required by the customer and send the alarm message in the specified order.

[0010] In some optional implementations, obtaining and saving the alarm message configuration file from the user management terminal includes:

[0011] Obtaining an alarm message configuration file, and writing data of the alarm message configuration file into a preset partition file, wherein the baseboard management controller is used to obtain data of the alarm message configuration file from the preset partition file;

[0012] Restart the server alarm process, where the server alarm process is used to obtain alarm messages and send the alarm messages to the user management end.

[0013] In this embodiment, the BMC writes the data of the alarm message configuration file into the preset partition file, overwriting the internal configuration file of the BMC system, so as to determine the alarm parameters and message sending order configured by the user when the server alarm is triggered. In addition, the entire BMC is not restarted, only the server alarm process is restarted, ensuring that the BMC normally monitors the health status of the server during the replacement of the configuration file.

[0014] In some optional implementations, determining the alarm parameters and the message sending order corresponding to the alarm parameters according to the alarm message configuration file, obtaining the alarm message corresponding to the alarm parameter, and sending the alarm message to the user management terminal according to the message sending order includes:

[0015] Access the preset partition file, and obtain the alarm parameter and the object identifier corresponding to the alarm parameter from the preset partition file;

[0016] Get the server logs;

[0017] According to the object identifier, the field corresponding to the alarm parameter is matched in the log, and the field is converted into an alarm message;

[0018] After the alarm message conversion is completed, the index number corresponding to the alarm parameter is obtained from the preset partition file, wherein the index number is used to determine the priority of the alarm message;

[0019] According to the index number, determine the order in which the messages corresponding to the alarm parameters are sent;

[0020] According to the message sending order, the alarm message and alarm parameters are sent to the user management end.

[0021] In this implementation, the BMC obtains the object identifier corresponding to the alarm parameter from the preset partition file, correctly identifies the information that the user needs to send, and no longer sends all the information, accurately matching and fully meeting the diverse needs of customers. In addition, the BMC sends the alarm message in the order of message sending set by the user, which is consistent with the user's reception, ensuring the orderliness and accuracy of the alarm message.

[0022] In some optional implementations, before determining the alarm parameters and the message sending order corresponding to the alarm parameters according to the alarm message configuration file, the method further includes:

[0023] Get the server's operating indicator data;

[0024] Determine whether the server fails based on the operating indicator data. If it is determined that the server fails, a server system alarm is triggered.

[0025] In a second aspect, the present invention provides a server alarm method, which is applied to a user management terminal and includes:

[0026] Obtain an alarm message configuration file, wherein the alarm message configuration file includes alarm parameters and a message sending order corresponding to the alarm parameters;

[0027] Sending an alarm message configuration file to a baseboard management controller, wherein the alarm message configuration file is used to instruct the baseboard management controller to obtain an alarm message corresponding to an alarm parameter when a server fails, and instruct the baseboard management controller to send the alarm message to a user management terminal according to a message sending order;

[0028] When a warning message is received from the baseboard management controller, the warning message is displayed.

[0029] In the server alarm method provided in this embodiment, the user management terminal sends the alarm message configuration file to the BMC, so that the BMC generates an alarm message according to the alarm message configuration file, realizes network equipment monitoring and alarm, and ensures stable operation of the server. In addition, the alarm message is displayed so that the user can determine the server status and customize the alarm parameters and message sending order contained in the alarm message configuration file as required, so as to meet diverse application requirements. The problem that the sent alarm message is not suitable for all customer application scenarios, and the parameters required by the customer cannot be retained and the alarm message cannot be sent in the specified order is solved.

[0030] In some optional implementations, obtaining the alarm message configuration file includes:

[0031] Get the preset configuration file from the baseboard management controller;

[0032] Obtaining a first modification instruction from a user for an alarm parameter and a second modification instruction for a message sending sequence;

[0033] According to the first modification instruction and the second modification instruction, the preset configuration file is modified, and the modified preset configuration file is used as the alarm message configuration file.

[0034] In this embodiment, the user controls the types and number of alarm messages sent by the BMC and the order in which the BMC sends alarm messages by adjusting the alarm parameters and message sending order included in the alarm message configuration file, thereby meeting diverse application requirements.

[0035] In some optional implementations, displaying a warning message includes:

[0036] Obtaining the index number corresponding to the alarm message from the management information base;

[0037] Determine the display order of the alarm messages according to the index numbers;

[0038] According to the display order, the alarm message and alarm parameters are displayed on the front-end interface.

[0039] In this embodiment, alarm messages and alarm parameters are displayed on the front-end interface according to the display order, so that users can determine the server status and customize the alarm parameters and message sending order contained in the alarm message configuration file as needed, thereby meeting diverse application needs.

[0040] In a third aspect, the present invention provides a server alarm device, which is deployed in a baseboard management controller and includes:

[0041] The first acquisition module is used to acquire and save the alarm message configuration file from the user management terminal;

[0042] The first sending module is used to determine the alarm parameters and the message sending order corresponding to the alarm parameters according to the alarm message configuration file when a server failure occurs, obtain the alarm message corresponding to the alarm parameters, and send the alarm message to the user management end according to the message sending order, instructing the user management end to display the alarm message.

[0043] In a fourth aspect, the present invention provides a server alarm device, which is deployed at a user management end and includes:

[0044] A second acquisition module is used to acquire an alarm message configuration file, wherein the alarm message configuration file includes alarm parameters and a message sending order corresponding to the alarm parameters;

[0045] A second sending module is used to send an alarm message configuration file to a baseboard management controller, wherein the alarm message configuration file is used to instruct the baseboard management controller to obtain an alarm message corresponding to an alarm parameter when a server fails, and instruct the baseboard management controller to send the alarm message to a user management terminal according to a message sending order;

[0046] The display module is used to display the alarm message when receiving the alarm message from the baseboard management controller.

[0047] In a fifth aspect, the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor are communicatively connected to each other, computer instructions are stored in the memory, and the processor executes the server alarm method of the above-mentioned first aspect or any corresponding embodiment thereof by executing the computer instructions, or executes the server alarm method of the above-mentioned second aspect or any corresponding embodiment thereof.

[0048] In a sixth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the server alarm method of the first aspect or any corresponding embodiment thereof, or to execute the server alarm method of the second aspect or any corresponding embodiment thereof.

[0049] In the seventh aspect, the present invention provides a computer program product, including computer instructions, which are used to enable a computer to execute the server alarm method of the above-mentioned first aspect or any corresponding embodiment, or to execute the server alarm method of the above-mentioned second aspect or any corresponding embodiment. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the related technologies, the drawings required for use in the specific embodiments or the related technical descriptions will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0051] Figure 1 is a flow chart of a server alarm method applied to a baseboard management controller according to an embodiment of the present invention;

[0052] Figure 2 is a schematic diagram of the contents of an alarm message configuration file according to an embodiment of the present invention;

[0053] Figure 3 is a flow chart of a server alarm method applied to a user management terminal according to an embodiment of the present invention;

[0054] Figure 4 is a schematic diagram of a front-end interface according to an embodiment of the present invention;

[0055] Figure 5 It is a schematic diagram of a method for customizing alarm events based on the network management protocol SNMP according to an embodiment of the present invention;

[0056] Figure 6 is a structural block diagram of a server alarm device deployed on a baseboard management controller according to an embodiment of the present invention;

[0057] Figure 7 is a structural block diagram of a server alarm device deployed at a user management terminal according to an embodiment of the present invention;

[0058] Figure 8 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0059] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0060] In the SNMP application framework, the collaborative work of the Manager and the Agent improves the flexibility and scalability of network management. As the core of the network management system, the Manager can actively collect and process information from each Agent to achieve comprehensive monitoring and management of network devices. The Agent, as a software entity on the network device, is responsible for collecting real-time status information of the device and sending trap messages to the Manager when necessary to promptly notify the network administrator of important events of the device. As a special communication method, the Trap message plays a vital role in the SNMP protocol. It allows the Agent to actively send notifications to the Manager when an important event is detected without waiting for the Manager's query. This method greatly improves the real-time and response speed of network management. At the same time, each Trap message contains rich information, and the binding variable information is the extended information of each Trap MIB (Management Information Base) node, including the reporting time, object identifier (OID), sensor information that triggers the alarm, event description, alarm level, event code, product serial number, product name, sensor type, event parameter information in event trigger mode, trigger time and other related information descriptions. This information provides sufficient context information for the Manager so that it can accurately understand and respond to the alarm. The Manager / Agent model and Trap message mechanism of SNMP provide strong support and guarantee for network management, allowing administrators to monitor and manage server devices more efficiently and ensure stability and security.

[0061] In the process of managing network nodes in an IP (Internet Protocol) network, the device containing the management software is used as the user management end, the SNMP application framework is used, the user management end is used as the Manager, and the BMC on each server motherboard is used as the Agent. SNMP trap alarm is a standard protocol used in (such as servers, workstations, routers, switches, etc.), and is widely used in the monitoring system of server clusters. It allows the BMC to actively send alarm information to the user management end. When the user management end receives the alarm message, it will refer to the MIB to parse the message. The MIB library is a database containing network device management information, which provides a common language and standard for communication between the Manager and the Agent. Based on the parsed information, users can understand the health status of server devices in real time and respond and handle problems quickly when they occur. Through SNMP trap alarms, users can monitor the device health information of the server cluster in real time, such as CPU usage, memory occupancy, fan failure, disk space, etc. Once an abnormality is found, they can immediately receive the trap alarm notification sent by the BMC and take corresponding measures to handle it. This can not only improve the stability and reliability of the system, but also reduce the risk and loss of failures. However, the variable attribute parameter configuration of the SNMPtrap alarm mechanism has many OID (Object Identifier) ​​parameters, which are not suitable for all customer application scenarios. Therefore, customers will make customized requirements to server manufacturers, only need to retain some OID and other parameters and instruct BMC to issue alarm information in a specific order. Multiple customers may have different requirements for this, which increases the manpower investment of developers and increases the company's investment. Currently, when the BMC management end detects an abnormality in the server device or function, the alarm mechanism will be triggered immediately. BMC will encapsulate these alarm attributes into the form of trap messages based on the key information fields in the server log and the mapping relationship between the alarm attributes and OID defined in the MIB, and then send them to the specified receiving end. Before the encapsulated alarm attributes are officially sent in the form of trap messages, the system preprocessing performed includes: encapsulating the alarm as an independent event, locking the event queue to ensure data consistency, safely putting it into the queue, and then unlocking the queue to continue subsequent operations. The variable attribute parameter configuration of the SNMPtrap alarm is set and completed in the BMC source code stage. Therefore, when the BMC management end issues an alarm, the alarm variable parameters received by the management user end strictly follow the queue order preset by the developer, and the user cannot directly modify these parameter configurations to ensure the stability and consistency of the system.

[0062] Based on the above content, an embodiment of the present invention provides a server alarm method, which flexibly adjusts the various attributes of SNMPtrap alarms according to the personalized needs and usage scenarios of users, so as to meet diverse application needs. Configure SNMPtrap alarm parameters, integrate them into the BMC system through configuration file reading and writing, realize network equipment monitoring and alarm, and ensure stable operation of the system. BMC correctly identifies the SNMPtrap attribute parameters that the user needs to send, and no longer sends all the information when sending an alarm message. In addition, BMC sends the alarm event parameters to the management end in a specific event queue sequence, which is consistent with the user's reception. In addition, users can also easily export configuration files to local storage to deal with special scenarios such as firmware upgrades that may cause the loss of configuration files. This design significantly enhances the scalability of the system and ensures the convenient reuse of configuration files. In order to achieve accurate matching and fully meet the diverse needs of customers, it can also significantly improve the quality of service while effectively reducing the workload of developers and the operating costs of enterprises.

[0063] According to an embodiment of the present invention, a server alarm embodiment is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a baseboard management controller, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0064] In this embodiment, a server alarm method is provided, which can be used to: Figure 1 is a flow chart of a server alarm method according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:

[0065] Step S101, obtaining and saving an alarm message configuration file from a user management terminal.

[0066] Specifically, the user logs in again to the BMC Web (network) management interface of the user management end, then selects and executes the operation of importing the configuration file, and uploads the alarm message configuration file saved locally in advance to the system website of the baseboard management controller (BMC). After completing the upload step, you need to confirm and save the relevant configuration options. The alarm message configuration file, for example: SNMPtrap.bak file, can be composed of an index number (Index), all event alarm attribute variable node OIDs, and variable descriptions. Among them, the Index field is used to determine the sending event queue order of the BMC alarm attribute variable node OID, and the event alarm attribute variable node OID is used to describe the alarm event attributes, which attributes are usually included. If the user does not want to receive the event field, the attribute variable node OID can be deleted. The variable description can explain the role of the attribute variable node OID to the user in a more friendly way. After the configuration file is integrated into the BMC, the BMC will not process the variable description field.

[0067] After receiving the alarm message configuration file, the BMC saves the alarm message configuration file uploaded by the user and restarts the SNMPtrap process of the BMC. The SNMPtrap process is used to execute step S102.

[0068] Step S102, in the event of a server failure, determine the alarm parameters and the message sending order corresponding to the alarm parameters according to the alarm message configuration file, obtain the alarm message corresponding to the alarm parameters, and send the alarm message to the user management end according to the message sending order, instructing the user management end to display the alarm message.

[0069] Specifically, BMC monitors the running status of the server. When BMC detects abnormalities in server equipment or functions, it triggers a server abnormality alarm. BMC will send alarm information to the specified user management terminal according to the alarm parameters and message sending order set in the alarm message configuration file. For example: when BMC monitors that the network card device on the server is overheated, it compares the temperature with the severe high temperature threshold and the irreversible high temperature threshold. If the temperature exceeds the threshold, it is determined that the network card is overheated, and the corresponding network card overheating alarm event is triggered.

[0070] The process includes determining the alarm parameters and the message sending order corresponding to the alarm parameters according to the alarm message configuration file. The alarm parameters are, for example, alarm OID (snmptrapOID), over-temperature severe alarm (trap Over TemperatureCritical High), alarm time (altTraptime), alarm sensor name (altSensorName), etc. The message sending order is, for example, sending the alarm message to the user management end according to the order of alarm OID, over-temperature severe alarm, alarm time, and alarm sensor name.

[0071] The BMC obtains the alarm message corresponding to the alarm parameter, for example, by searching the server system log for information matching the above alarm parameter as the alarm message. The alarm message is sent to the user management terminal according to the message sending order, and the user management terminal is instructed to display the alarm message.

[0072] The server alarm method provided in this embodiment, in the event of a server failure, determines the alarm parameters and the message sending order according to the alarm message configuration file sent by the user management end, obtains the alarm message corresponding to the alarm parameter, and sends the alarm message to the user management end according to the message sending order. The user can adjust the alarm parameters and message sending order contained in the alarm message configuration file to meet diverse application requirements. The alarm message sent by the baseboard management controller can accurately match and fully meet the diverse needs of customers. It solves the problem that the alarm message sent is not applicable to all customer application scenarios, and it is impossible to retain the parameters required by the customer and send the alarm message in the specified order.

[0073] In some optional implementations, obtaining and saving the alarm message configuration file from the user management terminal includes:

[0074] Obtaining an alarm message configuration file, and writing data of the alarm message configuration file into a preset partition file, wherein the baseboard management controller is used to obtain data of the alarm message configuration file from the preset partition file;

[0075] Restart the server alarm process, where the server alarm process is used to obtain alarm messages and send the alarm messages to the user management end.

[0076] Specifically, the alarm message configuration file sent by the user management terminal is obtained, and the internal configuration file of the BMC system, for example, the SNMPtrap.bak file, is overwritten. The data of the alarm message configuration file is written into a preset partition file, for example, the partition file SNMPtrap.ini of the BMC system.

[0077] After saving the alarm message configuration file uploaded by the user, the BMC front end will be triggered to send a message to the background system, so that the BMC automatically restarts the server alarm process. The server alarm process is, for example, the SNMPtrap process. The SNMPtrap process is used to execute step S102, obtain the alarm message and send the alarm message to the user management end. By restarting the SNMPtrap process, it is ensured that the newly uploaded configuration file content can be successfully written into the partition file SNMPtrap.ini of the BMC system.

[0078] In this embodiment, the BMC writes the data of the alarm message configuration file into the preset partition file, overwriting the internal configuration file of the BMC system, so as to determine the alarm parameters and message sending order configured by the user when the server alarm is triggered. In addition, the entire BMC is not restarted, only the server alarm process is restarted, ensuring that the BMC normally monitors the health status of the server during the replacement of the configuration file.

[0079] In some optional implementations, determining the alarm parameters and the message sending order corresponding to the alarm parameters according to the alarm message configuration file, obtaining the alarm message corresponding to the alarm parameter, and sending the alarm message to the user management terminal according to the message sending order includes:

[0080] Access the preset partition file, and obtain the alarm parameter and the object identifier corresponding to the alarm parameter from the preset partition file;

[0081] Get the server logs;

[0082] According to the object identifier, the field corresponding to the alarm parameter is matched in the log, and the field is converted into an alarm message;

[0083] After the alarm message conversion is completed, the index number corresponding to the alarm parameter is obtained from the preset partition file, wherein the index number is used to determine the priority of the alarm message;

[0084] According to the index number, determine the order in which the messages corresponding to the alarm parameters are sent;

[0085] According to the message sending order, the alarm message and alarm parameters are sent to the user management end.

[0086] Specifically, when the BMC detects an abnormality in a server component or function, such as overheating of components such as the CPU / network card, loss of fan power redundancy, or hard disk failure alarm, the BMC will trigger a system alarm, and the user-configured SNMPtrap alarm service will also be triggered synchronously. The BMC's SNMPtrap process will give priority to accessing preset partition files such as SNMPtrap.ini. This step is intended to retrieve the object identifier (OID) of the alarm parameters recorded in the alarm message configuration file. The preset partition file contains the index number (Index) and OID field information that need to be matched when the snmptrap alarm message recorded in the alarm message configuration file is sent, as well as the reporting time, object identifier, sensor information that triggered the alarm, event description, alarm level, and other information. Because the BMC writes the data of the alarm message configuration file to the preset partition file, the preset partition file includes all the data of the alarm message configuration file, such as Figure 2As shown, it includes: Index, OID and variable description. Index is as follows: 0, 1, 2, 3... OID is as follows: .1.3.6.1.2.1.1.3 (sysUpTime, system upload time), .1.3.6.1.6.3.1.1.4.1 (snmp Trap OID, alarm OID)... Variable description is as follows: The time in hundredths of a second kmanagement portion of the system was last re-initialized (the time when the system management portion was last re-initialized is in hundredths of a second)... For details, see Figure 2 , I will not go into details here.

[0087] The SNMPtrap process of the BMC obtains the object identifier (OID) corresponding to the alarm parameter from the preset partition file. The SNMPtrap process of the BMC obtains the logs of the server, such as the System Event Log (SEL), the Diagnostic Log (IDL), etc. The SEL is a log file that records various events that occur in the system. These events can include hardware failures, software errors, system startup and shutdown, etc. The information recorded by the SEL can help determine the root cause of the problem and provide important clues about the health of the system.

[0088] According to the object identifier (OID), these alarm parameters are then accurately matched with the corresponding field information in the above log, the fields corresponding to the alarm parameters are matched, and the fields are converted into alarm messages, namely trap message information; among them, the reporting time, sensor and alarm level of the SNMPtrap alarm message correspond to the timestamp, sensor name and severity fields reported by the SEL one by one.

[0089] After the alarm message conversion is completed, the SNMPtrap process reads the preset partition file and obtains the index number (Index) corresponding to the alarm parameter from the preset partition file. The priority of the alarm message can be determined by the Index.

[0090] According to the index number, determine the message sending order corresponding to the alarm parameter, for example: follow the order of the Index value from small to large to traverse all field information, and ensure that the OID field value corresponding to the Index is sent to the user management end in order. According to the message sending order, send the alarm message and alarm parameters to the user management end, so that the BMC can issue an alarm according to the alarm attribute variable node of the SNMPtrap configuration file in the set event queue order.

[0091] In this implementation, the BMC obtains the object identifier corresponding to the alarm parameter from the preset partition file, correctly identifies the information that the user needs to send, and no longer sends all the information, accurately matching and fully meeting the diverse needs of customers. In addition, the BMC sends the alarm message in the order of message sending set by the user, which is consistent with the user's reception, ensuring the orderliness and accuracy of the alarm message.

[0092] In some optional implementations, before determining the alarm parameters and the message sending order corresponding to the alarm parameters according to the alarm message configuration file, the method further includes:

[0093] Get the server's operating indicator data;

[0094] Determine whether the server fails based on the operating indicator data. If it is determined that the server fails, a server system alarm is triggered.

[0095] Specifically, the operating indicator data of the server is obtained, such as the temperature of the CPU / network card and other devices on the server, the fan speed / power supply data, the hard disk read and write speed per second, etc.

[0096] Determine whether the server has a fault based on the operation indicator data. For example, the BMC monitors the temperature of the network card device on the server and compares the temperature with the severe high temperature threshold and the irreversible high temperature threshold. If the temperature exceeds the threshold, the network card is determined to be overheated and the corresponding network card overheating alarm event is triggered. Server failures also include: CPU / network card and other components overheating, fan power redundancy loss, hard disk failure alarm, etc. At this time, the BMC will trigger the server system alarm, and the user-configured SNMPtrap alarm service will also be triggered synchronously.

[0097] In some optional implementations, in step S102, the BMC is required to determine whether a server failure occurs, and the determination process may include steps A1 to A6.

[0098] Step A1, set a preset threshold range for key indicator data of server hardware operation, and set status information of the hardware operation status corresponding to the preset threshold range. The key indicator data of server hardware operation include CPU temperature data, voltage data of designated points on the motherboard, and fan speed data. The preset threshold range includes a normal threshold range, a warning threshold range, and an alarm threshold range. The status information of the hardware operation status includes normal status information corresponding to the normal threshold range, warning status information corresponding to the warning threshold range, and alarm status information corresponding to the alarm threshold range, wherein the warning status information and the alarm status information are both abnormal status information.

[0099] Step A2: Associating different status information of the hardware running status with hardware status indicator lights of different colors respectively.

[0100] In step A3, the BMC obtains the key indicator data of the server hardware operation, and determines the preset threshold range of the key indicator data of the hardware operation. If the key indicator data of the hardware operation is in the normal threshold range, it corresponds to normal state information; if the key indicator data of the hardware operation is in the warning threshold range, it corresponds to warning state information; if the key indicator data of the hardware operation is in the alarm threshold range, it corresponds to alarm state information.

[0101] Step A4, BMC transmits the key indicator data of the server hardware operation and the corresponding status information of each hardware to the front-end Web interface through the dbus (message bus) interface; at the same time, BMC screens out abnormal status information, and then appends the abnormal status information and the corresponding key indicator data of the hardware operation to the server's Event (event) log, and sends the abnormal status information and the corresponding key indicator data of the hardware operation to the remote management workstation through SNMP. The BMCEvent log includes real-time data such as the server's CPU temperature, voltage at specific points on the board, and fan speed.

[0102] Step A5: the server lights up a hardware status indicator light of a corresponding color according to the hardware status information.

[0103] Step A6: The front-end Web interface displays the key operating indicator data of each hardware of the server in specific colors on the front-end Web interface according to the status information of each hardware.

[0104] In this embodiment, the BMC event log is presented on the front-end web interface, and corresponding prompts can be made through the server alarm light to notify the operation and maintenance management personnel, which greatly reduces the more serious consequences of server failures. When the key indicator data of the server hardware operation is in the normal threshold range, warning threshold range and alarm threshold range, they will be displayed in different colors, which is more convenient to distinguish the severity of the server failure, so that the operation and maintenance management personnel can solve the corresponding server failure more targeted. The operation and maintenance efficiency of the operation and maintenance management personnel is greatly improved, and the occurrence of situations caused by server failures is further reduced, thereby improving the overall security of the server.

[0105] According to an embodiment of the present invention, an embodiment of a server alarm method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in the user management terminal, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that here.

[0106] In this embodiment, a server alarm method is provided, which can be used for a user management terminal. Figure 3 is a flow chart of a server alarm method according to an embodiment of the present invention. Figure 3 As shown, the process includes the following steps:

[0107] Step S301: Acquire an alarm message configuration file, wherein the alarm message configuration file includes alarm parameters and a message sending sequence corresponding to the alarm parameters.

[0108] Specifically, the user modifies the variable attribute parameter configuration of the SNMPtrap alarm mechanism, for example, by adding or deleting alarm parameters, adjusting the message sending order corresponding to the alarm parameters, and generates an alarm message configuration file and saves it locally. The alarm message configuration file is, for example, the SNMPtrap.bak file.

[0109] The user management end is a device that contains management software. When users use the SNMPtrap service, they need to set the alarm policy in advance on the BMC management page, including the destination (the server address IP that receives the alarm information sent in the trap mode), port number (SNMPtrap service port number 162) and other fields. The target machine here refers to the user management end. The user logs in to the BMC Web management interface of the user management end again, then selects and executes the operation of importing the configuration file, and uploads the alarm message configuration file saved locally in advance to the system website of the baseboard management controller (BMC). After completing the upload step, you need to confirm and save the relevant configuration options.

[0110] Step S302, sending an alarm message configuration file to a baseboard management controller, wherein the alarm message configuration file is used to instruct the baseboard management controller to obtain an alarm message corresponding to an alarm parameter when a server fails, and instruct the baseboard management controller to send the alarm message to a user management terminal according to a message sending order.

[0111] Specifically, the alarm message configuration file is sent to the BMC. The BMC monitors the server's operating status. When the BMC detects that the server device or function is abnormal, the server abnormality alarm is triggered. The BMC will send the alarm information to the designated user management terminal according to the alarm parameters and message sending order set in the alarm message configuration file. For example: When the BMC monitors that the network card device on the server is overheated, the temperature is compared with the severe high temperature threshold and the irreversible high temperature threshold. If the temperature exceeds the threshold, it is determined that the network card is overheated, and the corresponding network card overheating alarm event is triggered.

[0112] The process includes determining the alarm parameters and the message sending order corresponding to the alarm parameters according to the alarm message configuration file. The alarm parameters are, for example, alarm OID (snmptrapOID), trap Over Temperature Critical High, alarm time (altTraptime), alarm sensor name (altSensorName), etc. The message sending order is, for example, sending the alarm message to the user management end according to the order of alarm OID, trap Over Temperature Critical High, alarm time, and alarm sensor name. The BMC obtains the alarm message corresponding to the alarm parameter, for example, searching the server system log for information matching the above alarm parameters as the alarm message. The alarm message is sent to the user management end according to the message sending order, and the user management end is instructed to display the alarm message.

[0113] Step S303: when receiving an alarm message from the baseboard management controller, display the alarm message.

[0114] Specifically, when an alarm message is received from the baseboard management controller, the user management terminal automatically parses the alarm message into the format required by the SNMPtrap message, and displays an intuitive and clear alarm message to the user on the front-end interface of the management software of the user management terminal.

[0115] In the server alarm method provided in this embodiment, the user management terminal sends the alarm message configuration file to the BMC, so that the BMC generates an alarm message according to the alarm message configuration file, realizes network equipment monitoring and alarm, and ensures stable operation of the server. In addition, the alarm message is displayed so that the user can determine the server status and customize the alarm parameters and message sending order contained in the alarm message configuration file as required, so as to meet diverse application requirements. The problem that the sent alarm message is not suitable for all customer application scenarios, and the parameters required by the customer cannot be retained and the alarm message cannot be sent in the specified order is solved.

[0116] In some optional implementations, obtaining the alarm message configuration file includes:

[0117] Get the preset configuration file from the baseboard management controller;

[0118] Obtaining a first modification instruction from a user for an alarm parameter and a second modification instruction for a message sending sequence;

[0119] According to the first modification instruction and the second modification instruction, the preset configuration file is modified, and the modified preset configuration file is used as the alarm message configuration file.

[0120] Specifically, a preset configuration file is obtained from the baseboard management controller. For example, the preset configuration file is an initial variable attribute parameter configuration file of the SNMPtrap alarm mechanism. The variable attribute parameter configuration file has been set in the source code stage of the BMC, including the reporting time, object identifier (OID), sensor information that triggers the alarm, event description, alarm level, event code, product serial number, product name, sensor type, etc.

[0121] The user determines the required alarm parameters and the order in which the alarm messages are expected to be obtained according to the application scenario. The alarm parameters in the preset configuration file are modified according to the required alarm parameters, for example, adding or deleting, and a first modification instruction is generated. The message sending order is modified according to the order in which the alarm messages are expected to be obtained, for example, the Index corresponding to different OIDs is modified, and a second modification instruction is generated.

[0122] The user management terminal obtains the user's first modification instruction for the alarm parameters and the second modification instruction for the message sending order, modifies the preset configuration file according to the first modification instruction and the second modification instruction, and uses the modified preset configuration file as the alarm message configuration file. In addition, the alarm message configuration file is saved locally, which has high reusability and scalability;

[0123] It should be noted that the content of the snmptrap configuration file in this embodiment only covers variables such as the snmptrap version, alarm level, and user name, and does not constrain the content of the snmptrap alarm information. This is a further optimization of the snmptrap configuration file.

[0124] In this embodiment, the user controls the types and number of alarm messages sent by the BMC and the order in which the BMC sends alarm messages by adjusting the alarm parameters and message sending order included in the alarm message configuration file, thereby meeting diverse application requirements.

[0125] In some optional implementations, displaying a warning message includes:

[0126] Obtaining the index number corresponding to the alarm message from the management information base;

[0127] Determine the display order of the alarm messages according to the index numbers;

[0128] According to the display order, the alarm message and alarm parameters are displayed on the front-end interface.

[0129] Specifically, when the user management terminal receives the alarm message, the user management terminal will automatically retrieve and match the corresponding OID from the MIB library (Management Information Library), and obtain the index number (Index) corresponding to the alarm message from the MIB library.

[0130] Once the user management end completes the background data processing flow, it automatically parses the alarm message into the format required by the SNMPtrap message. The user management end displays the alarm message and alarm parameters to the user intuitively and clearly on the front-end interface of the management software. For example: determine the display order corresponding to the alarm message according to the index number, and display the alarm message and alarm parameters in the order from small to large Index values. The display order can be the same as the message sending order. Figure 4 As shown in the figure, the front-end interface displays the BMCIP (BMC Internet Protocol address) and the alarm messages received by the user management end, including fields such as snmptrapOID (alarm OID), altTraptime (alarm time), and altSensorName (alarm sensor name). The display order is consistent with the order in which the BMC sends alarm messages. For details, see Figure 4 , which is convenient for users to handle server exceptions immediately. It converts the SNMPtrap alarm event attribute variable node OID into the corresponding structure or string content, and presents the OID information to users in text form, so that users can customize and adjust according to their needs.

[0131] In this embodiment, alarm messages and alarm parameters are displayed on the front-end interface according to the display order, so that users can determine the server status and customize the alarm parameters and message sending order contained in the alarm message configuration file as needed, thereby meeting diverse application needs.

[0132] In some optional implementations, a method for customizing alarm events based on the network management protocol SNMP is provided, which can also solve the problem that the sent alarm message is not applicable to all customer application scenarios, and the parameters required by the customer cannot be retained and the alarm message cannot be sent in a specified order. Figure 5 As shown, the method includes:

[0133] Export the SNMPtrap configuration file to the local computer through the Web; edit and modify the node order and node options locally; upload and modify the saved SNMPtrap configuration file through the Web.

[0134] Specifically, users configure SNMP trap alarm parameters through the user management end, and integrate them into the BMC system through configuration file reading and writing, so as to realize network equipment monitoring and alarm, and ensure the stable operation of the system. BMC correctly identifies the SNMPtrap OID attribute parameters that users need to send, and no longer sends all OIDs. BMC sends alarm event parameters to the management end in a specific event queue order, which is consistent with what users receive.

[0135] In this implementation, users can customize SNMP alarm node parameters, which can be accurately and timely sent to the Agent, thereby effectively meeting the personalized customization needs of different customers. This method is widely applicable to various types of servers, demonstrating its strong adaptability and application value. This method has high universality, flexibility and scalability.

[0136] In this embodiment, a server alarm device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0137] This embodiment provides a server alarm device, which is deployed in a baseboard management controller, such as Figure 6 As shown, including:

[0138] The first acquisition module 601 is used to acquire and save the alarm message configuration file from the user management terminal;

[0139] The first sending module 602 is used to determine the alarm parameters and the message sending order corresponding to the alarm parameters according to the alarm message configuration file when a server failure occurs, obtain the alarm message corresponding to the alarm parameters, and send the alarm message to the user management end according to the message sending order, instructing the user management end to display the alarm message.

[0140] In some optional implementations, the first acquisition module 601 acquires and saves the alarm message configuration file from the user management terminal, including:

[0141] Obtaining an alarm message configuration file, and writing data of the alarm message configuration file into a preset partition file, wherein the baseboard management controller is used to obtain data of the alarm message configuration file from the preset partition file;

[0142] Restart the server alarm process, where the server alarm process is used to obtain alarm messages and send the alarm messages to the user management end.

[0143] In some optional implementations, the first sending module 602 determines the alarm parameters and the message sending order corresponding to the alarm parameters according to the alarm message configuration file, obtains the alarm message corresponding to the alarm parameter, and sends the alarm message to the user management terminal according to the message sending order, including:

[0144] Access the preset partition file, and obtain the alarm parameter and the object identifier corresponding to the alarm parameter from the preset partition file;

[0145] Get the server logs;

[0146] According to the object identifier, the field corresponding to the alarm parameter is matched in the log, and the field is converted into an alarm message;

[0147] After the alarm message conversion is completed, the index number corresponding to the alarm parameter is obtained from the preset partition file, wherein the index number is used to determine the priority of the alarm message;

[0148] According to the index number, determine the order in which the messages corresponding to the alarm parameters are sent;

[0149] According to the message sending order, the alarm message and alarm parameters are sent to the user management end.

[0150] In some optional implementations, before determining the alarm parameters and the message sending order corresponding to the alarm parameters according to the alarm message configuration file, the apparatus is used to:

[0151] Get the server's operating indicator data;

[0152] Determine whether the server fails based on the operating indicator data. If it is determined that the server fails, a server system alarm is triggered.

[0153] This embodiment provides a server alarm device, which is deployed at a user management end, such as Figure 7 As shown, including:

[0154] The second acquisition module 701 is used to acquire an alarm message configuration file, wherein the alarm message configuration file includes alarm parameters and a message sending order corresponding to the alarm parameters;

[0155] The second sending module 702 is used to send the alarm message configuration file to the baseboard management controller, wherein the alarm message configuration file is used to instruct the baseboard management controller to obtain the alarm message corresponding to the alarm parameter when a server fails, and instruct the baseboard management controller to send the alarm message to the user management terminal according to the message sending order;

[0156] The display module 703 is used to display the alarm message when the alarm message is received from the baseboard management controller.

[0157] In some optional implementations, the second acquisition module 701 acquires the alarm message configuration file, including:

[0158] Get the preset configuration file from the baseboard management controller;

[0159] Obtaining a first modification instruction from a user for an alarm parameter and a second modification instruction for a message sending sequence;

[0160] According to the first modification instruction and the second modification instruction, the preset configuration file is modified, and the modified preset configuration file is used as the alarm message configuration file.

[0161] In some optional implementations, the display module 703 displays the warning message, including:

[0162] Obtaining the index number corresponding to the alarm message from the management information base;

[0163] Determine the display order of the alarm messages according to the index numbers;

[0164] According to the display order, the alarm message and alarm parameters are displayed on the front-end interface.

[0165] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0166] The server alarm device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0167] The embodiment of the present invention also provides a computer device having the above Figure 6 or Figure 7 The server alarm device is shown.

[0168] See also Figure 8 , Figure 8 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 8 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 8 A processor 10 is taken as an example.

[0169] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include an integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0170] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.

[0171] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0172] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0173] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0174] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0175] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of the computer program instruction in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc., and accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.

[0176] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined in this application.

Claims

1. A server alarm method, characterized in that: The method is applied to a baseboard management controller, and the method comprises: Obtain and save the alarm message configuration file from the user management terminal; In the event of a server failure, the alarm parameters and the message sending order corresponding to the alarm parameters are determined according to the alarm message configuration file, the alarm message corresponding to the alarm parameters is obtained, and the alarm message is sent to the user management end according to the message sending order, instructing the user management end to display the alarm message.

2. The method according to claim 1, characterized in that The step of obtaining and saving the alarm message configuration file from the user management terminal includes: Obtaining the alarm message configuration file, and writing data of the alarm message configuration file into a preset partition file, wherein the baseboard management controller is used to obtain the data of the alarm message configuration file from the preset partition file; Restarting the server alarm process, wherein the server alarm process is used to obtain the alarm message and send the alarm message to the user management terminal.

3. The method according to claim 2, characterized in that The determining, according to the alarm message configuration file, alarm parameters and a message sending order corresponding to the alarm parameters, obtaining an alarm message corresponding to the alarm parameters, and sending the alarm message to the user management terminal according to the message sending order, includes: Accessing the preset partition file, and obtaining the alarm parameter and the object identifier corresponding to the alarm parameter from the preset partition file; Obtaining a log of the server; According to the object identifier, matching the field corresponding to the alarm parameter in the log, and converting the field into the alarm message; After the alarm message conversion is completed, obtaining an index number corresponding to the alarm parameter from the preset partition file, wherein the index number is used to determine the priority of the alarm message; Determine, according to the index number, the message sending order corresponding to the alarm parameter; The alarm message and the alarm parameters are sent to the user management terminal according to the message sending order.

4. The method according to claim 1, characterized in that Before determining the alarm parameters and the message sending order corresponding to the alarm parameters according to the alarm message configuration file, the method further includes: Obtaining operation indicator data of the server; It is determined whether the server fails based on the operation indicator data, and if it is determined that the server fails, a server system alarm is triggered.

5. A server alarm method, characterized in that: The method is applied to a user management terminal, and the method comprises: Obtaining an alarm message configuration file, wherein the alarm message configuration file includes alarm parameters and a message sending order corresponding to the alarm parameters; Sending the alarm message configuration file to a baseboard management controller, wherein the alarm message configuration file is used to instruct the baseboard management controller to obtain an alarm message corresponding to the alarm parameter when a server fails, and instruct the baseboard management controller to send the alarm message to the user management terminal according to the message sending order; In case the warning message is received from the baseboard management controller, the warning message is displayed.

6. The method according to claim 5, characterized in that The step of obtaining the alarm message configuration file includes: Obtaining a preset configuration file from the baseboard management controller; Obtaining a first modification instruction from a user for the alarm parameter and a second modification instruction for the message sending order; According to the first modification instruction and the second modification instruction, the preset configuration file is modified, and the modified preset configuration file is used as the alarm message configuration file.

7. The method according to claim 5, characterized in that The displaying of the warning message includes: Obtaining the index number corresponding to the alarm message from the management information base; Determine the display order of the warning messages according to the index numbers; According to the display order, the alarm message and the alarm parameters are displayed on the front-end interface.

8. A server alarm device, characterized in that: The device is deployed in a baseboard management controller, and the device includes: The first acquisition module is used to acquire and save the alarm message configuration file from the user management terminal; The first sending module is used to determine the alarm parameters and the message sending order corresponding to the alarm parameters according to the alarm message configuration file when a server failure occurs, obtain the alarm message corresponding to the alarm parameters, and send the alarm message to the user management terminal according to the message sending order, instructing the user management terminal to display the alarm message.

9. A server alarm device, characterized in that: The device is deployed at the user management end, and the device includes: A second acquisition module is used to acquire an alarm message configuration file, wherein the alarm message configuration file includes alarm parameters and a message sending order corresponding to the alarm parameters; A second sending module is used to send the alarm message configuration file to a baseboard management controller, wherein the alarm message configuration file is used to instruct the baseboard management controller to obtain an alarm message corresponding to the alarm parameter when a server fails, and instruct the baseboard management controller to send the alarm message to the user management terminal according to the message sending order; The display module is used to display the alarm message when the alarm message is received from the baseboard management controller.

10. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the server alarm method according to any one of claims 1 to 7 by executing the computer instructions.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the server alarm method according to any one of claims 1 to 7.

Images