Anomaly Determination Methods and Related Devices
By querying the behavior information of the application client and the expander, and displaying its status using CLI commands, the accuracy problem of expansion card anomaly detection was solved, and timely and accurate status determination was achieved.
Patent Information
- Application Number
- CN202211710263.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-12-29
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2042-12-29
AI Technical Summary
In existing technologies, expansion cards may malfunction during use, affecting the service capabilities of storage servers and making it impossible to determine their status in a timely and accurate manner.
By querying the application behavior information of the application client and the response behavior information of the expansion card, and displaying the status of the expansion using CLI commands, including determining whether the response behavior has timed out, query behavior frequency, control behavior records, and Zone configuration records, the abnormal status of the expansion can be determined.
It enables timely and accurate determination of the expander's state, improving the accuracy and reliability of anomaly detection.
Smart Images

Figure CN115964213B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of computers, and in particular to an anomaly determination method and related apparatus. Background Technology
[0002] With the continuous expansion of cloud computing and data center construction, the demand for high-density data storage is constantly growing, making storage servers an application trend. For servers, expansion cards are typically used on the server's hard drive backplane to connect more hard drives, thereby expanding storage capacity.
[0003] However, since the Expander card may malfunction during use, affecting the service capabilities of the storage server, timely and accurate determination of the Expander's status has become an urgent problem for those in the field. Summary of the Invention
[0004] In view of the above problems, the present invention provides an anomaly determination method and related apparatus to overcome or at least partially solve the above problems.
[0005] Firstly, an anomaly determination method includes:
[0006] Query at least one of the following: application behavior information of the application client and response behavior information of the expansion card, wherein the application client is in a communication connection with the expansion card;
[0007] Based on the information obtained from the query, the state of the Expander is determined, wherein the state reflects whether the Expander is abnormal;
[0008] The status of the Expander is displayed using CLI commands.
[0009] In conjunction with the first aspect, in some optional implementations, the query of at least one of the application behavior information of the application client and the response behavior information of the expansion card includes:
[0010] The query retrieves multiple response behavior records from the response behavior information of the Expander, where each response behavior record corresponds to one response behavior of the Expander, and each response behavior record includes corresponding response time information.
[0011] Determining the state of the Expander based on the information obtained from the query includes:
[0012] Based on the response time information recorded for each of the aforementioned response behaviors, determine whether any of the aforementioned response behaviors timed out;
[0013] If a timeout occurs, the Expander's state is determined to be abnormal.
[0014] If there is no timeout response, the Expander is determined to be in a normal state.
[0015] In conjunction with the first aspect, in some optional implementations, the query of at least one of the application behavior information of the application client and the response behavior information of the expansion card includes:
[0016] Multiple query behavior records are obtained from the application behavior information of the application client. Each query behavior record corresponds to a query behavior of the application client for the Expander. Each query behavior record includes corresponding query time information.
[0017] Determining the state of the Expander based on the information obtained from the query includes:
[0018] The frequency of each query behavior is determined based on the query time information recorded for each query behavior.
[0019] The state of the Expander is determined based on the frequency of each query behavior.
[0020] In conjunction with the previous implementation method, in some optional implementation methods, determining the state of the Expander based on the frequency of each query behavior includes:
[0021] Determine whether any of the frequencies of the query behaviors exceed the corresponding preset frequency threshold;
[0022] If there is a frequency that exceeds the corresponding preset frequency threshold, then the Expander's state is determined to be an abnormal state;
[0023] If there is no frequency exceeding the corresponding preset frequency threshold, then the Expander is determined to be in a normal state.
[0024] In conjunction with the first aspect, in some optional implementations, the query of at least one of the application behavior information of the application client and the response behavior information of the expansion card includes:
[0025] Query whether there is a control behavior record in the application behavior information of the application client, wherein one control behavior record corresponds to one control behavior of the application client on the Expander;
[0026] Determining the state of the Expander based on the information obtained from the query includes:
[0027] If the aforementioned control behavior record exists, then the Expander's state is determined to be an abnormal state;
[0028] If no record of the control behavior exists, the Expander is determined to be in a normal state.
[0029] In conjunction with the first aspect, in some optional implementations, the query of at least one of the application behavior information of the application client and the response behavior information of the expansion card includes:
[0030] The application client retrieves multiple Zone configuration records from its application behavior information. Each Zone configuration record corresponds to a first configuration function of the Zone, and each Zone configuration record corresponds to a Zone configuration command.
[0031] Determining the state of the Expander based on the information obtained from the query includes:
[0032] Determine whether the multiple Zone configuration records in the application behavior information include all Zone configuration commands corresponding to the first configuration function;
[0033] If multiple Zone configuration records in the application behavior information do not include all Zone configuration commands corresponding to the first configuration function, then the Expander's state is determined to be abnormal.
[0034] If multiple Zone configuration records in the application behavior information include all Zone configuration commands corresponding to the first configuration function, then the Expander's state is determined to be normal.
[0035] In conjunction with the first aspect, in some optional implementations, the application behavior information includes: first command information and second command information, wherein the first command information includes the start time of the first command initiation, the interval time of the first command processing, the command code of the first command, the page code of the first command, and the command type of the first command, and the second command information includes the start time of the second command initiation, the interval time of the second command processing, and the function command of the second command.
[0036] Secondly, an anomaly determination method includes: an information query unit, a status determination unit, and a status display unit;
[0037] The information query unit is used to query at least one of the application behavior information of the application client and the response behavior information of the expansion card, wherein the application client is communicatively connected to the expansion card.
[0038] The state determination unit is used to determine the state of the Expander based on the information obtained from the query, wherein the state reflects whether the Expander is abnormal;
[0039] The status display unit is used to display the status of the Expander based on CLI commands.
[0040] Thirdly, a computer-readable storage medium having a program stored thereon, which, when executed by a processor, implements the exception determination method described in any of the preceding claims.
[0041] Fourthly, an electronic device includes at least one processor, at least one memory and a bus connected to the processor; wherein the processor and the memory communicate with each other via the bus; the processor is configured to invoke program instructions in the memory to execute the exception determination method described in any of the preceding claims.
[0042] By employing the above technical solution, the present invention provides an anomaly determination method and related apparatus. This method can determine the state of the Expander by querying at least one of the following: application behavior information from an application client and response behavior information from an expansion card. The application client and the Expander are communicatively connected. Based on the queried information, the state of the Expander is determined, indicating whether the Expander is abnormal. The state of the Expander is displayed using CLI commands. Therefore, it can be seen that the present invention can determine the state of the Expander promptly and accurately based on recorded information, with a high accuracy rate.
[0043] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, and in order to make the above and other objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description
[0044] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:
[0045] Figure 1 A flowchart of the first anomaly determination method provided by the present invention is shown;
[0046] Figure 2 A schematic diagram of an anomaly determination device provided by the present invention is shown;
[0047] Figure 3 A schematic diagram of the structure of an electronic device provided by the present invention is shown. Detailed Implementation
[0048] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this invention will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.
[0049] like Figure 1 As shown, the present invention provides an anomaly determination method, including: S100, S200 and S300;
[0050] S100: Query at least one of the application behavior information of the application client and the response behavior information of the expansion card, wherein the application client is in a communication connection with the expansion card;
[0051] Optionally, the execution entity of this invention can be the chip of the Expander expansion card, that is, the scheme of this invention is executed through the chip of the Expander expansion card. The application client can initiate various application actions to the storage server. This invention can record relevant information about these application actions to facilitate subsequent determination of the Expander's state based on this information; this invention does not impose any limitations on this.
[0052] Optionally, as mentioned above, the Expander acts as an intermediary between the server and the hard drive. The server needs to perform corresponding operations on the hard drive through the Expander to respond to application behaviors from the application client. Because the executing entity of this invention can record response behavior information related to the application client's response behavior, it can subsequently determine the state of the Expander based on this information; this invention does not impose any limitations on this.
[0053] S200. Based on the information obtained from the query, determine the state of the Expander, wherein the state reflects whether the Expander is abnormal;
[0054] Optionally, the present invention may have multiple embodiments, and different embodiments use different information to determine the state of Expander. The present invention may determine the state of Expander based solely on application behavior information, or solely on response behavior information, or by combining application behavior information and response behavior information.
[0055] S300: Display the status of the Expander using CLI command.
[0056] Optionally, CLI command methods are well-known concepts in the art, and this invention will not describe them in detail; please refer to relevant descriptions in the art for specific details. For example, if the Expander's state is determined to be "abnormal," the word "abnormal" can be displayed on the corresponding display interface or an indicator light can be turned on.
[0057] Optionally, CLI commands can display the Expander's status via the serial port (physical serial port) and BMC SOL (BMC function).
[0058] For example, combining Figure 1 In some optional embodiments, the illustrated implementation includes step 1.1;
[0059] Step 1.1: Query and obtain multiple response behavior records in the response behavior information of the Expander, wherein each response behavior record corresponds to one response behavior of the Expander, and each response behavior record includes corresponding response time information;
[0060] S200 includes: steps 1.2, 1.3, and 1.4;
[0061] Step 1.2: Based on the response time information recorded for each of the aforementioned response behaviors, determine whether any response behaviors have timed out.
[0062] If a timeout occurs, proceed to step 1.3; otherwise, proceed to step 1.4.
[0063] Step 1.3: Determine that the Expander's state is an abnormal state;
[0064] Step 1.4: Determine that the Expander is in a normal state.
[0065] Optionally, taking two adjacent response behavior records as an example, the response time information corresponding to the two response behavior records is T1 and T0, respectively, where T1 is later than T0. The present invention can calculate the time interval of T1 minus T0. If the time interval is greater than a preset time threshold, it indicates that the response behavior corresponding to T1 has timed out; otherwise, it indicates that the response behavior corresponding to T1 has not timed out.
[0066] For example, this invention can obtain response behavior records for SCSI commands or SMP commands, and can count the maximum response time corresponding to each response behavior record, and then determine whether the maximum response time meets industry standards or customer standards (preset time thresholds). If the response times out, in addition to determining that the expander is in an abnormal state, it can also further discover certain problems in the firmware design.
[0067] Optional, combined Figure 1 In some optional implementations of the illustrated embodiments, the application behavior information includes: first command information and second command information, wherein the first command information includes the start time of the first command initiation, the interval time of the first command processing, the command code of the first command, the page code of the first command, and the command type of the first command, and the second command information includes the start time of the second command initiation, the interval time of the second command processing, and the function command of the second command.
[0068] For example, the first command information can be the data information corresponding to the SCSI command. The specific data structure corresponding to the SCSI command is as follows:
[0069] SAS_ADDRESS src_sas_addr; -- The SAS address of the SSP Initiator for the Application Client;
[0070] UINT32 start_time; -- The start time of the command.
[0071] UINT32 during_time; -- The interval for command processing (return time minus start time);
[0072] UINT8 scsi_code; -- scsi command;
[0073] UINT8 page_code;--page code;
[0074] UINT8 ctrl_status; -- control or status.
[0075] The start time of the first command mentioned above is the specific content corresponding to `start_time`. The processing interval of the first command mentioned above is the specific content corresponding to `during_time`. The command code of the first command mentioned above is the specific content corresponding to `scsi_code`. The page code of the first command mentioned above is the specific content corresponding to `page_code`. The command type of the first command mentioned above is the specific content corresponding to `ctrl_status`, where `control` represents a control command and `status` represents a status query command.
[0076] For example, the second command information can be the data information corresponding to the SMP command. The specific data structure corresponding to the SMP command is as follows:
[0077] SAS_ADDRESS src_sas_addr; -- The address of the SMP Initiator SAS for the Application Client;
[0078] UINT32 start_time; -- The start time of the command.
[0079] UINT32 during_time; -- The interval for command processing (return time minus start time);
[0080] UINT8 smp_func; -- smp function command.
[0081] The start time of the second command mentioned above is the specific content corresponding to `start_time`. The processing interval of the second command mentioned above is the specific content corresponding to `during_time`. The function command of the second command mentioned above is the specific content corresponding to `smp_func`.
[0082] For example, combining Figure 1 In some optional embodiments of the implementation shown, S100 includes: step 2.1;
[0083] Step 2.1: Query and obtain multiple query behavior records in the application behavior information of the application client, wherein each query behavior record corresponds to a query behavior of the application client for the Expander, and each query behavior record includes corresponding query time information;
[0084] S200 includes: steps 2.2 and 2.3;
[0085] Step 2.2: Determine the frequency of each query behavior based on the query time information recorded in each query behavior record;
[0086] Step 2.3: Determine the state of the Expander based on the frequency of each query behavior.
[0087] Optionally, this invention can determine what command the application client sends to obtain Expander information by recording Receive Diagnostic Results, SES Page 02h. Then, by comparing the occurrence time (query time information) of the two previous occurrences in the recorded Receive Diagnostic Results, SES Page 02h, the frequency of the application client's Expander queries can be determined (which can also be characterized by time intervals).
[0088] It should be noted that Receive Diagnostic Results supports standard pages such as 02h, 05h, and 0ah. Logging these pages allows us to know what commands the application client sent to obtain Expander information.
[0089] Since Receive Diagnostic Results (SES) Page 02h is quite important because it directly queries the machine's status, the frequency of the application client's Expander query can be determined by calculating the difference between the occurrence times of the two occurrences.
[0090] For example, in conjunction with the previous embodiment, in some optional embodiments, step 2.3 includes: steps 3.1, 3.2 and 3.3;
[0091] Step 3.1: Determine whether any of the frequencies of the query behaviors exceed the corresponding preset frequency threshold;
[0092] If there is a frequency that exceeds the corresponding preset frequency threshold, proceed to step 3.2; if there is no frequency that exceeds the corresponding preset frequency threshold, proceed to step 3.3.
[0093] Step 3.2: Determine that the Expander's state is an abnormal state;
[0094] Step 3.3: Determine that the Expander is in a normal state.
[0095] Optionally, as mentioned above, a time interval can be calculated for each of two adjacent query records, and the time interval reflects the corresponding frequency. Therefore, this invention can calculate multiple frequencies for multiple query records. This invention can then determine whether each frequency exceeds a preset frequency threshold.
[0096] For example, combining Figure 1 In some optional embodiments of the implementation shown, S100 includes: step 4.1;
[0097] Step 4.1: Query whether there is a control behavior record in the application behavior information of the application client, wherein one control behavior record corresponds to one control behavior of the application client on the Expander;
[0098] S200 includes: steps 4.2 and 4.3;
[0099] Step 4.2: If the control behavior record exists, then determine that the Expander's state is an abnormal state;
[0100] Step 4.3: If no control behavior record exists, the Expander is determined to be in a normal state.
[0101] Optionally, the present invention can determine whether the application client has performed corresponding control actions on the Expander (such as controlling the hard drive power and LEDs) by recording the Send Diagnostic Results, 02h. These control actions are generally application actions that the application client will only take when the Expander malfunctions. Therefore, the present invention can determine the state of the Expander based on whether there are corresponding control action records, and the present invention does not impose any limitations on this.
[0102] For example, combining Figure 1 In some optional embodiments of the implementation shown, S100 includes: step 5.1;
[0103] Step 5.1: Query and obtain multiple Zone configuration records in the application behavior information of the application client, wherein each of the multiple Zone configuration records corresponds to the first configuration function of the Zone, and each Zone configuration record corresponds to a Zone configuration command;
[0104] S200 includes: steps 5.2, 5.3, and 5.4;
[0105] Step 5.2: Determine whether the multiple Zone configuration records in the application behavior information include all Zone configuration commands corresponding to the first configuration function;
[0106] If the multiple Zone configuration records in the application behavior information do not include all Zone configuration commands corresponding to the first configuration function, then proceed to step 5.3; if the multiple Zone configuration records in the application behavior information include all Zone configuration commands corresponding to the first configuration function, then proceed to step 5.4.
[0107] Step 5.3: Determine that the Expander's state is an abnormal state;
[0108] Step 5.4: Determine that the Expander is in a normal state.
[0109] Optionally, this invention can determine whether the application client has executed the Zone configuration function of the SMP command by recording the SMP RequestZone Lock,86h (or any Zone-related configuration command). Generally, a Zone configuration function requires the sequential execution of multiple Zone configuration commands to complete; that is, under normal circumstances, a Zone configuration function should correspond to multiple Zone configuration records (records corresponding to all Zone configuration commands for that Zone configuration function). If the application behavior information only contains a portion of the Zone configuration records corresponding to a Zone configuration function, it indicates a configuration problem, and the Expander state can be determined to be abnormal.
[0110] For example, configuring Zone requires executing 6 commands, namely:
[0111] SMP ZONE LOCK;
[0112] SMP CONFIGURE ZONE PHY INFORMATION;
[0113] SMP CONFIGURE ZONE PERMISSION TABLE;
[0114] SMP ENABLE DISABLE ZONING;
[0115] SMP ZONEACTIVATE;
[0116] SMP ZONE UNLOCK.
[0117] Missing any command can cause Zone configuration to fail. By analyzing incomplete command logs, it can be determined that the Zone configuration is not taking effect.
[0118] Optionally, if the Expander is determined to be in an abnormal state, the present invention can check the Zone configuration, because if the Zone configuration is incorrect, the hard drive will be difficult to identify.
[0119] Optional, combined Figure 1 In some optional embodiments, after S200, the method further includes sending the state of the Expander to the application client via an in-band method.
[0120] Optionally, the In-band approach refers to adding an OEM SES Page, which collects data via the Page and sends it to the application client for display.
[0121] Optionally, by displaying the data in-band (Expander function), you can design an OEM SES Page to save the recorded data for later analysis by the tool.
[0122] like Figure 2 As shown, the present invention provides an anomaly determination method, including: an information query unit 100, a status determination unit 200, and a status display unit 300;
[0123] The information query unit 100 is used to query at least one of the application behavior information of the application client and the response behavior information of the expansion card, wherein the application client is communicatively connected to the expansion card.
[0124] The state determination unit 200 is used to determine the state of the Expander based on the information obtained from the query, wherein the state reflects whether the Expander is abnormal;
[0125] The status display unit 300 is used to display the status of the Expander based on CLI command.
[0126] Combination Figure 2 In some optional embodiments, the information query unit 100 shown in the embodiments includes: a first query subunit;
[0127] The first query subunit is used to query and obtain multiple response behavior records in the response behavior information of the Expander, wherein one response behavior record corresponds to one response behavior of the Expander, and each response behavior record includes corresponding response time information;
[0128] The state determination unit 200 includes: a timeout determination subunit, a first abnormal subunit, and a first normal subunit;
[0129] The timeout determination subunit is used to determine whether there is a timeout response behavior among the response behaviors based on the response time information recorded in each response behavior record.
[0130] The first abnormal subunit is used to determine that the Expander's state is abnormal if there is a timeout response behavior;
[0131] The first normal subunit is used to determine that the Expander is in a normal state if there is no timeout response behavior.
[0132] Combination Figure 2 In some optional embodiments, the information query unit 100 shown in the embodiments includes: a second query subunit;
[0133] The second query subunit is used to query and obtain multiple query behavior records in the application behavior information of the application client, wherein each query behavior record corresponds to a query behavior of the application client for the Expander, and each query behavior record includes corresponding query time information;
[0134] The state determination unit 200 includes: a frequency determination subunit and a state determination subunit;
[0135] The frequency determination subunit is used to determine the frequency of each query behavior based on the query time information of each query behavior record;
[0136] The state determination subunit is used to determine the state of the Expander based on the frequency of each query behavior.
[0137] In conjunction with the previous implementation, in some optional implementations, the state determination subunit includes: a frequency determination subunit, a second abnormal subunit, and a second normal subunit;
[0138] The frequency determination subunit is used to determine whether there are frequencies in each query behavior that exceed the corresponding preset frequency threshold.
[0139] The second abnormal subunit is used to determine that the Expander's state is abnormal if there is a frequency that exceeds the corresponding preset frequency threshold.
[0140] The second normal subunit is used to determine that the Expander is in a normal state if there is no frequency exceeding the corresponding preset frequency threshold.
[0141] Combination Figure 2 In some optional embodiments, the information query unit 100 shown in the embodiments includes: a third query subunit;
[0142] The third query subunit is used to query whether there is a control behavior record in the application behavior information of the application client, wherein one control behavior record corresponds to one control behavior of the application client on the Expander;
[0143] The state determination unit 200 includes: a third abnormal subunit and a third normal subunit;
[0144] The third abnormal subunit is used to determine that the Expander's state is abnormal if the control behavior record exists.
[0145] The third normal subunit is used to determine that the Expander is in a normal state if no control behavior record exists.
[0146] Combination Figure 2 In some optional embodiments, the information query unit 100 shown in the embodiments includes: a fourth query subunit;
[0147] The fourth query subunit is used to query and obtain multiple Zone configuration records in the application behavior information of the application client, wherein each of the multiple Zone configuration records corresponds to the first configuration function of the Zone, and each Zone configuration record corresponds to a Zone configuration command;
[0148] The state determination unit 200 includes: a configuration determination subunit, a fourth abnormal subunit, and a fourth normal subunit;
[0149] The configuration determination subunit is used to determine whether the multiple Zone configuration records in the application behavior information include all Zone configuration commands corresponding to the first configuration function.
[0150] The fourth abnormal subunit is used to determine that the Expander is in an abnormal state if multiple Zone configuration records in the application behavior information do not include all Zone configuration commands corresponding to the first configuration function.
[0151] The fourth normal subunit is used to determine that the Expander is in a normal state if multiple Zone configuration records in the application behavior information include all Zone configuration commands corresponding to the first configuration function.
[0152] Combination Figure 2 In the illustrated implementation, in some optional embodiments, the apparatus further includes: a result transmission unit;
[0153] The result sending unit is used to send the state of the Expander to the application client via an in-band method after determining the state of the Expander based on the information obtained from the query.
[0154] The present invention provides a computer-readable storage medium having a program stored thereon, which, when executed by a processor, implements the exception determination method described in any of the preceding claims.
[0155] like Figure 3 As shown, the present invention provides an electronic device 70, which includes at least one processor 701, at least one memory 702 and a bus 703 connected to the processor 701; wherein the processor 701 and the memory 702 communicate with each other through the bus 703; the processor 701 is used to call program instructions in the memory 702 to execute the exception determination method described above.
[0156] In this invention, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, without necessarily requiring or implying any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0157] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.
[0158] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined in this invention may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the invention 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.
[0159] The above description is merely a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention are included within the scope of protection of the present invention.
Claims
1. An anomaly determination method characterized by comprising: include: The query records at least one of the following: application behavior information of the application client and response behavior information of the expansion card, wherein the application client is communicatively connected to the expansion card, the application behavior information includes the historical records of the operation behavior initiated by the application client to the expansion card, and the response behavior information includes the historical response records of the expansion card to the operation issued by the application client. Based on the information obtained from the query, the state of the Expander is determined, wherein the state reflects whether the Expander is abnormal; The status of the Expander is displayed using CLI commands; The application behavior information includes: first command information and second command information. The first command information includes the start time of the first command initiation, the interval time of the first command processing, the command code of the first command, the page code of the first command, and the command type of the first command. The second command information includes the start time of the second command initiation, the interval time of the second command processing, and the function command of the second command.
2. The method according to claim 1, characterized in that, The query record contains at least one of the following: application behavior information of the application client and response behavior information of the expansion card. The query retrieves multiple response behavior records from the response behavior information of the Expander, where each response behavior record corresponds to one response behavior of the Expander, and each response behavior record includes corresponding response time information. Determining the state of the Expander based on the information obtained from the query includes: Based on the response time information recorded for each of the aforementioned response behaviors, determine whether any of the aforementioned response behaviors timed out; If a timeout occurs, the Expander's state is determined to be abnormal. If there is no timeout response, the Expander is determined to be in a normal state.
3. The method according to claim 1, characterized in that, The query record contains at least one of the following: application behavior information of the application client and response behavior information of the expansion card. Multiple query behavior records are obtained from the application behavior information of the application client. Each query behavior record corresponds to a query behavior of the application client for the Expander. Each query behavior record includes corresponding query time information. Determining the state of the Expander based on the information obtained from the query includes: The frequency of each query behavior is determined based on the query time information recorded for each query behavior. The state of the Expander is determined based on the frequency of each query behavior.
4. The method according to claim 3, characterized in that, Determining the state of Expander based on the frequency of each query behavior includes: Determine whether any of the frequencies of the query behaviors exceed the corresponding preset frequency threshold; If there is a frequency that exceeds the corresponding preset frequency threshold, then the Expander's state is determined to be an abnormal state; If there is no frequency exceeding the corresponding preset frequency threshold, then the Expander is determined to be in a normal state.
5. The method according to claim 1, characterized in that, The query record contains at least one of the following: application behavior information of the application client and response behavior information of the expansion card. Query whether there is a control behavior record in the application behavior information of the application client, wherein one control behavior record corresponds to one control behavior of the application client on the Expander; Determining the state of the Expander based on the information obtained from the query includes: If the aforementioned control behavior record exists, then the Expander's state is determined to be an abnormal state; If no record of the control behavior exists, the Expander is determined to be in a normal state.
6. The method according to claim 1, characterized in that, The query record contains at least one of the following: application behavior information of the application client and response behavior information of the expansion card. The application client retrieves multiple Zone configuration records from its application behavior information. Each Zone configuration record corresponds to a first configuration function of the Zone, and each Zone configuration record corresponds to a Zone configuration command. Determining the state of the Expander based on the information obtained from the query includes: Determine whether the multiple Zone configuration records in the application behavior information include all Zone configuration commands corresponding to the first configuration function; If multiple Zone configuration records in the application behavior information do not include all Zone configuration commands corresponding to the first configuration function, then the Expander's state is determined to be abnormal. If multiple Zone configuration records in the application behavior information include all Zone configuration commands corresponding to the first configuration function, then the Expander's state is determined to be normal.
7. An anomaly detection device, characterized in that, include: Information query unit, status determination unit, and status display unit; The information query unit is used to query at least one of the following: application behavior information of the application client and response behavior information of the expansion card. The application client is communicatively connected to the expansion card. The application behavior information includes the historical records of the operation behavior initiated by the application client to the expansion card. The response behavior information includes the historical response records of the expansion card to the operation issued by the application client. The state determination unit is used to determine the state of the Expander based on the information obtained from the query, wherein the state reflects whether the Expander is abnormal; The status display unit is used to display the status of the Expander based on CLI command. The application behavior information includes: first command information and second command information. The first command information includes the start time of the first command initiation, the interval time of the first command processing, the command code of the first command, the page code of the first command, and the command type of the first command. The second command information includes the start time of the second command initiation, the interval time of the second command processing, and the function command of the second command.
8. A computer-readable storage medium having a program stored thereon, characterized in that, When the program is executed by the processor, it implements the exception determination method as described in any one of claims 1 to 6.
9. An electronic device, characterized in that, The electronic device includes at least one processor, and at least one memory and a bus connected to the processor; wherein the processor and the memory communicate with each other through the bus; the processor is used to call program instructions in the memory to execute the anomaly determination method as described in any one of claims 1 to 6.
Citation Information
Patent Citations
Method for reading information and serial small computer system interface SAS expander
CN110941580A
Expander chip hang-up repairing method and system and related device
CN111324486A
